zoho_campaigns_get_bounced_contacts

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

With no annotations, the description discloses that the tool is read-only (does not delete contacts). This adds some behavioral context, but lacks details on rate limits, authorization, or behavior with empty parameters, resulting in moderate transparency.

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 very concise with two short sentences. However, the negative note about not deleting could be integrated into the behavior description, but overall it is front-loaded and efficient.

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 two parameters and no output schema, the description should cover both input and output. It partially explains input (listkeys) but omits explanation for max_contacts and does not describe the return format or pagination, leaving gaps for a simple tool.

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?

With 0% schema description coverage, the description should explain the parameters. It vaguely mentions scanning lists (implying listkeys) but does not define max_contacts or clarify the format and purpose of listkeys, leaving the agent to infer critical details.

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 the tool scans lists and returns bounced contacts, with a specific verb and resource. It also distinguishes itself by noting it does not delete contacts, but it could be clearer in differentiating from sibling tools like get_campaign_bounces or get_list_contacts.

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 explicit guidance on when to use this tool versus sibling tools. The description only notes that contacts are not deleted due to Zoho constraints, but fails to provide context for appropriate use cases or alternatives.

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