zoho_save_draft

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds the key behavioral fact that nothing is sent, plus the threading mechanism, but says nothing about account/auth requirements or what a successful save returns.

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, the non-sending constraint is front-loaded, and the follow-up sentence covers the one non-obvious parameter case. No filler.

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 13-parameter mutation tool with no output schema, the description covers purpose and one advanced parameter but omits mode semantics (draft vs template default), attachment usage, and the fromAddress ownership rule. Adequate minimum but with clear gaps against the tool's complexity.

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 69%, so most parameters are self-documented, and inReplyTo/refHeader already carry examples in the schema. The description adds only derivational guidance ('from the original email's headers'), which is a marginal gain rather than compensating for the uncovered parameters.

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 (save) and resource (email as draft/template) and explicitly contrasts with sending ('without sending it'), which distinguishes it from zoho_send_email and zoho_reply_to_email. It does not name those siblings directly, so 4 rather than 5.

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 one concrete usage condition – how to produce a threaded reply draft via inReplyTo/refHeader – but never states when to choose this over zoho_send_email or zoho_reply_to_email, nor any prerequisites. Usage is implied rather than enumerated.

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