mailchimp_campaigns_get_content

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves content, which implies a read-only operation, but it does not disclose additional behavioral traits such as permissions required, response format details, or any side effects. The verb 'Get' provides basic transparency but nothing more.

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?

The description is a single sentence with no unnecessary words. It directly states the action and the output, making it highly efficient and front-loaded.

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?

For a simple tool with one required parameter and no output schema, the description adequately explains what the tool returns ('HTML and plain-text content'). It is sufficient for an agent to understand the tool's purpose, though it lacks usage guidance and behavioral context that would make it fully 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?

The schema covers the only parameter (campaign_id) with a description 'Campaign ID', so schema_description_coverage is 100%. The description adds no additional parameter semantics; it merely reiterates that the tool is for a campaign.

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 uses the specific verb 'Get' and clearly identifies the resource ('a campaign') and the deliverable ('HTML and plain-text content'). This distinguishes it from siblings like 'mailchimp_campaigns_get' and 'mailchimp_campaigns_set_content'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it is for retrieving content specifically, nor does it contrast with related tools such as 'mailchimp_campaigns_get' or 'mailchimp_campaigns_set_content'.

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