zoho_download_inline_image

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the phrase 'to the local disk' is consistent with writing a file locally, so there is no contradiction. Beyond that, the description adds little: no mention of overwrite behavior, error handling if contentId is not an inline image, or permission needs. With annotations covering the safety profile, a 3 is appropriate.

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 tight sentences with the action and destination front-loaded and the parameter hint second. Every clause carries information; nothing is padded or repeated.

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 file-download tool with no output schema, the description covers what it does, where it writes, and how to obtain the non-obvious contentId. Remaining gaps (overwrite/error behavior, whether it also writes to the server mailbox) are minor but not fully addressed.

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 80% and the schema documents saveTo's default path, fileName, folderId, and messageId. The description adds value for the one undocumented parameter (contentId), explaining it is the cid returned by zoho_get_attachment_info — meaning beyond what the bare schema provides.

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 and resource ('Download an inline image of an email') and adds the destination ('to the local disk'). This implicitly distinguishes it from the sibling zoho_download_attachment (normal attachment) and zoho_get_attachment_info, but it never names those siblings explicitly, so the differentiation is left to inference.

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?

Points the agent to the prerequisite tool and required flag: contentId comes from zoho_get_attachment_info with includeInline=true. That is clear usage context, but there is no explicit 'use this instead of X' routing or any when-not guidance.

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