mailchimp_campaigns_get

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

With no annotations, the description carries all responsibility for behavioral disclosure. It only states a read operation but does not mention what fields are returned, potential error conditions, rate limits, or any authentication sensitivity. Minimal transparency beyond the operation itself.

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, front-loaded sentence with no extraneous words. It is structurally clean, though slightly under-specified for a full understanding. Still, it earns its place as a concise summary.

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?

Given the simplicity of a one-parameter get-by-ID tool with no output schema, the description is minimally viable but does not clarify what 'details' includes or what the response shape will be. This is adequate for an agent to attempt the call, but not enough to anticipate the result.

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?

Schema description coverage is 100% (campaign_id is described as 'Campaign ID'), so the description adds no extra meaning beyond the schema. The baseline of 3 applies since the parameter is self-explanatory and no additional semantics are needed.

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 identifies the action ('Get'), the resource ('details for a specific campaign'), and the key discriminator 'by ID'. This distinguishes it from list or content-specific operations, though 'details' is somewhat generic given siblings like get_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 usage guidance is provided. The description does not explain when to use this tool versus alternatives such as mailchimp_campaigns_get_content, get_send_checklist, or campaigns_list. No context about preferred scenarios or exclusions.

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