zoho_download_attachment

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

With readOnlyHint=false, the description usefully discloses the actual side effect (a file is written to local disk) and the return value (the saved path), which matters given there is no output schema. It does not mention overwrite behavior or failure/error cases, so it is good but not exhaustive.

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 action and effect, then the prerequisite. No filler; every clause earns its place.

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 five-parameter download tool with no output schema, the definition covers purpose, side effect, return value, and where to obtain IDs. Remaining gaps (overwrite semantics, error behavior, and the default saveTo path already in the schema) are minor.

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 100%, so the baseline would be 3; however, the description adds provenance meaning by stating that attachmentId and fileName come from zoho_get_attachment_info, saving the agent a discovery step. It leaves the other parameters (folderId, messageId, saveTo) entirely to 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?

States a specific verb+resource+effect: 'Download an email attachment to the local disk and return the saved path.' This distinguishes it from the metadata-only sibling zoho_get_attachment_info and from zoho_download_inline_image, which is confirmed by the second sentence routing the agent to zoho_get_attachment_info for IDs.

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?

Gives clear prerequisite guidance by naming zoho_get_attachment_info as the source of attachmentId and the file name, which tells the agent where this tool sits in the workflow. It stops short of explicit when-not-to-use conditions or contrasting it with zoho_upload_attachment/zoho_download_inline_image, so it does not reach a 5.

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