zoho_get_email_content

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that the returned payload is the HTML body (helpful since there is no output schema), but says nothing about the format of surrounding structure, whether attachments/quotes are dropped, or how includeBlockContent changes output.

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?

A single front-loaded sentence with no filler; it is efficient and readable. It is arguably too thin for a tool with three parameters, but nothing in it is wasted.

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, the description should carry more of the return-value burden; stating 'body (HTML)' is the minimum. It omits any note on authentication, error conditions, or how the required folderId/messageId pair is obtained, leaving substantial context to the schema.

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 description coverage is 100% and the schema itself explains string-encoded 64-bit IDs and the includeBlockContent flag, so the baseline is 3. The description contributes nothing beyond 'body (HTML)' and does not clarify interactions between the 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?

The description states a specific verb and resource ('Get the body (HTML) of an email'), and the parenthetical '(HTML)' usefully distinguishes it from header/metadata siblings. However it never names the closely related tools (zoho_get_email_metadata, zoho_get_email_headers, zoho_get_original_message), so an agent must infer the boundary itself.

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?

There is no guidance on when to call this versus fetching metadata, headers, or the original message, and no stated prerequisites (e.g. needing a folderId from zoho_list_folders). The only hint of usage context lives in the schema, not the description.

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