zoho_list_emails

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

Annotations already declare this a read-only, open-world operation, so the safety profile is covered. The description adds genuine context beyond that: the default ordering (newest first), the cross-folder behavior when folderId is omitted, and the full set of returned fields in the absence of an output schema.

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 compact sentences, with the scoping/ordering rule front-loaded and the return-field list following. The field enumeration is justified because no output schema exists, though it is a long untokenized run of field names.

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 16-parameter list tool with no output schema, the description usefully compensates by naming returned fields and stating default ordering and folder scope. It stops short of explaining pagination semantics (limit/start together) or which filters combine, which would be the remaining gaps for an agent.

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 75%, so most parameters are documented in the schema; the description still adds meaning by disclosing the default sort direction and the semantic effect of omitting folderId. It does not clarify interaction between sortBy/sortorder or the start/limit pagination contract, leaving some room.

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?

States a specific verb (List) and resource (emails) with scope (a folder, or across folders when folderId is omitted) and default ordering. It does not explicitly distinguish itself from the sibling zoho_search_emails, so an agent must infer the enumeration-vs-search split rather than being told.

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 parenthetical 'across folders if folderId is omitted' gives an implied usage condition, but there is no explicit when-to-use/when-not guidance and no routing to the obvious alternative (zoho_search_emails) for query-driven retrieval. Usage is inferable but not stated.

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