mailchimp_search_campaigns

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

With no annotations, the description carries the burden of conveying safety and behavior. 'Search' implies a read-only operation, and 'all campaigns' adds scope, but it does not explicitly disclose that no modifications occur, note rate limits, or detail response behavior. This is a moderate level of transparency for a search tool.

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, well-structured sentence that is front-loaded with the key action and resource. It is concise and free of unnecessary words or repetition.

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 search tool with three parameters and no output schema, the description is adequate but minimal. It does not mention the structure of the response or provide details about pagination beyond what the schema implies. Given the lack of an output schema, some additional context about return values would improve completeness.

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 input schema already provides descriptions for all three parameters (count, query, offset) with 100% coverage. The description adds only a generic mention of 'query terms,' which aligns with the query parameter but provides no additional semantic value beyond the schema.

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 a specific action (search) on a specific resource (all campaigns in the account) for query terms. This distinguishes it from sibling tools like mailchimp_campaigns_list (which lists campaigns) and mailchimp_search_members (which searches members).

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?

The description implies the tool is used when you need to find campaigns by keyword or phrase, which is distinct from listing all campaigns or getting a specific campaign. However, it does not explicitly mention alternatives or exclusion criteria, so it lacks a clear when-not-to-use.

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