zoho_get_attachment_info

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that inline images and their cid can be surfaced on request, but says nothing about pagination, ordering, or behavior when no attachments exist.

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?

One front-loaded sentence with the resource first and the optional behavior trailing; no filler. Arguably a touch dense with the parenthetical field list, but every clause carries 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?

For a read-only tool with no output schema, naming the returned fields is the key completeness requirement, and that is done. Only minor gaps (ordering, empty-result behavior) remain, which matter little for an info-listing call.

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 documents folderId and messageId (including the string-precision caveat), and the description supplies the missing semantics for includeInline by explaining it pulls in inline images with their cid. That closes the 67% coverage gap with real meaning added beyond the schema.

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?

Specific verb (List) plus resource (attachments of an email), and it even enumerates the returned fields (attachmentId, attachmentName, attachmentSize). It is clearly separable from sibling download_attachment or get_email_content, though it doesn't name those siblings explicitly.

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 guidance on when to use this vs neighbors like zoho_get_email_metadata, zoho_get_email_content, or zoho_download_attachment. The purpose implies the use case, but no prerequisites or alternatives are stated.

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