mailchimp_search

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

With no annotations, the description carries the full burden. It discloses search scope and result outcomes (subscriber_hash, campaign_id), but does not explicitly confirm it is a read-only operation or mention limitations like pagination or rate limits. It adds useful context but leaves some behavioral aspects implicit.

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 two sentences, front-loaded with 'Search the account' and immediately gives examples. It uses a clear 'Set action to one of:' structure with inline definitions, making it concise and scannable with no wasted 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?

For a search tool with three parameters and no output schema, the description adequately covers the search scope and action semantics. It lacks explicit response format details, but it provides enough context for an agent to select and invoke the tool correctly, and the action enum details fill in key gaps.

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 coverage is 100%, so baseline is 3. The description adds meaning to the 'action' parameter by elaborating on each enum value (members finds subscribers, campaigns finds campaigns), and reinforces that query can be an email, name, or phrase. This goes beyond the schema's brief reference to the tool description.

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 'Search the account' and provides concrete examples (email to subscriber_hash, phrase to campaign_id) and enumerates two action types with detailed explanations. This distinguishes it from sibling tools like mailchimp_members and mailchimp_campaigns by positioning it as an account-wide search.

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?

It explicitly positions the tool as 'the fastest way' for specific lookups and explains each action's scope (find subscribers across all audiences, find campaigns by title/subject/content). It does not name alternative tools or state when not to use it, but the context implies it is the go-to for cross-account searches.

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