zoho_campaigns_bounced_contact_policy

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 'explains' something, implying it is a read-only retrieval with no side effects. However, it does not explicitly confirm safety or disclose any behavioral traits beyond that.

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, concise sentence that conveys the tool's purpose with no extraneous information.

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?

The tool has no parameters or output schema, and the description does not specify the format or structure of the returned policy explanation. For a simple informational tool, this is adequate but not 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 input schema has no parameters and 100% coverage, so the description does not need to add parameter meaning. The description correctly avoids misleading parameter info. Score elevated due to zero parameters.

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 specifies the tool explains Zoho's policy on bounced contacts ('Explica qué permite Zoho respecto de contactos devueltos'). It distinguishes it from sibling tools, which are action-oriented (e.g., get_bounced_contacts, move_to_do_not_mail). However, the phrasing could be more explicit (e.g., 'Retrieve the Zoho Campaigns policy on bounced 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 when-to-use or when-not-to-use guidance is provided. Since the tool is purely informational, usage is implied for understanding policy before performing related actions, but alternatives are not mentioned.

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