verify_connected_site_script

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate non-read-only. Description adds that it respects read-only/dry-run modes, has max 10 concurrent requests, and is API-key authenticated. No contradictions. Provides useful behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (description, usage, args, returns). Each sentence is necessary and front-loaded with purpose. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all aspects: purpose, usage order, parameters, auth, concurrency, modes, and return value. Output schema exists. Complete for a verification tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, the description includes an Args section explaining both parameters: connected_site_id source and account optionality/default. This adds meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Verify' and resource 'Mailchimp tracking script installed on a connected site'. It also provides context: run after create_connected_site, and distinguishes from get_connected_site.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('Run after installing the script...') and when not to use ('Use get_connected_site to check...'). Also mentions auth, concurrency limits, and mode support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.