get_campaign_send_checklist

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

Adds beyond annotations: 'Read-only, safe to retry,' authentication requirement, and concurrency limit. Annotations already indicate readOnlyHint and destructiveHint, so this adds value. No contradiction.

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 separate sections for purpose, usage, auth, parameters, and returns. Every sentence adds value without redundancy. Not verbose.

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 prerequisites (campaign ID), explains return format (JSON with is_ready and items array, each item including type, id, heading, details), and output schema exists. Adequate for a two-parameter 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?

With 0% schema description coverage, the description fully compensates by explaining campaign_id sources (list_campaigns/search_campaigns) and account parameter usage including environment variable convention and default behavior.

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 'Retrieve the pre-send readiness checklist for a campaign,' specifying a unique verb-resource combination. It distinguishes itself from sibling tools like get_campaign_details by focusing on readiness validation.

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 to verify a campaign is ready before sending' and instructs to resolve errors before calling send_campaign. Also references get_campaign_details for IDs. Lacks explicit when-not-to-use but provides clear context.

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