zoho_fetch

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

With no annotations, the description carries the burden but only adds authentication and automatic token refresh behavior. It does not disclose error handling, rate limits, response format, or the fact that this is a raw API wrapper with no validation.

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?

Two short sentences, front-loaded with the core purpose. The second sentence adds scope without redundancy.

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 generic 5-parameter tool with no output schema, the description gives only the essential authentication context. It lacks guidance on expected response behavior, error cases, or differentiation from more specific tools like calendar_today, making it adequate but not 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?

Schema description coverage is 100%, so all parameter meanings are already documented in the schema. The description adds no additional parameter-level detail beyond what the schema provides, keeping the baseline score at 3.

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's function with a specific verb ('Make an authenticated Zoho API call') and identifies the resource (Zoho APIs). It also distinguishes itself from siblings by being a generic authenticated fetch, while no other sibling covers raw Zoho API calls.

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 usage for Zoho API calls and names supported services (Mail, Calendar, other), but provides no explicit when-to-use vs alternatives, exclusions, or precedence. Sibling tools like calendar_today and crm_search might overlap, but the description does not clarify when to prefer this generic fetch.

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