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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the mutation and external-dependency profile is known. The description adds genuine value by disclosing the required auth artifacts and their source, but says nothing about re-connection behavior, failure modes, or what the tool 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 short sentences, front-loaded with the action and followed by prerequisites. Nothing is padded.

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?

With no output schema and 6 parameters at 50% coverage, the description covers the credential-acquisition flow but leaves the return value, the 'dc'/'name' parameters, and post-connection behavior undocumented. Adequate for the happy path but incomplete for an agent that needs to handle edge cases.

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 50%, and the description compensates partially by explaining where client_id/client_secret/code come from. The 'dc' (data centre) and 'name' parameters are left entirely to the schema, and neither the description nor schema documents 'name' at all.

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 ('Connect a Zoho Mail mailbox') and scopes it to the Zoho API, which implicitly distinguishes it from the generic connect_imap_mailbox sibling. It does not explicitly name that alternative, so differentiation is inferential rather than stated.

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?

Prerequisites are given (Self Client id, secret, generated code from api-console.zoho.com), which tells the agent what must be gathered first. However, there is no explicit when-to-use-this-vs-connect_imap_mailbox statement or note about what happens if the mailbox is already connected.

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