get_campaign_send_checklist

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

Annotations already set readOnlyHint=true. Description adds that the tool returns is_ready boolean and an items array with type, id, heading, details, which is beyond annotations. No contradictions.

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?

Description is concise (~80 words), well-structured with Args/Returns sections, no fluff, and front-loaded with purpose.

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 purpose, usage, return structure, and references siblings. However, missing explanation for the 'account' parameter, and no mention of potential errors or caching, though read-only tool reduces need. Slight gap.

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?

Description explains campaign_id (source from list_campaigns/search_campaigns) but ignores the optional 'account' parameter entirely. Schema coverage is 0%, so description should cover both parameters; missing one leaves a gap.

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?

Description clearly states 'Retrieve the pre-send readiness checklist for a campaign', specifying verb and resource. It distinguishes from sibling get_campaign_details by noting that IDs come from that tool, and from send_campaign by positioning as a pre-check.

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 says use before sending, resolve 'error' items before calling send_campaign, and get IDs from get_campaign_details. Provides clear when-to-use and alternatives.

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