get_campaign_advice

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

Discloses 404 error for invalid campaign_id and empty advice array for no suggestions, beyond annotations which already indicate read-only.

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?

Concise, well-structured with sections: purpose, usage, error cases, arguments, return format. No unnecessary words.

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, errors, parameter semantics, and return structure. Output schema exists to detail return, so complete.

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?

Describes campaign_id with example and constraint, but account parameter is not explained (though optional and default null). Schema has 0% coverage, so description compensates well.

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 it retrieves Mailchimp's automated post-send feedback on a campaign, differentiating from siblings like get_campaign_report.

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 ('to surface algorithmic suggestions') and when not ('use get_campaign_report for raw metrics'), plus constraint 'only works for sent campaigns'.

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