Add endpoint pattern examples to execute tool description

[mattzcarey]

Summary

• Adds guidance that not all Cloudflare API endpoints follow the same pattern — some are top-level (e.g. /zones, /user) with query filters, others are nested under /accounts/{account_id}/
• Adds two concrete examples: listing zones (top-level with account.id query filter) and listing Workers scripts (account-scoped)
• Adds a note to always use the search tool first to find the correct endpoint path

Context

Another MCP client was hitting errors by using /accounts/{id}/zones instead of /zones?account.id={id}. These examples should help models pick the right pattern.

Test plan

• Verify examples render correctly in tool description
• Test that /zones with query filter works
• Test that /accounts/{accountId}/workers/scripts works