zoho_get_email_metadata

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. In the absence of an output schema, the description's enumeration of returned fields adds genuine transparency about what comes back, but it says nothing about auth, rate limits, or failure behavior for a non-existent/inaccessible message.

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 naming the operation before the field list; zero filler. The parenthetical list is dense but every item is informative, so it earns its length.

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 simple two-required-param read tool, this is nearly complete: the safety annotation covers the read semantics, the schema fully documents the inputs, and the description compensates for the missing output schema by listing the returned fields. Only the sibling boundary (metadata vs headers vs content) remains unaddressed.

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 already documents both folderId and messageId thoroughly, including the string-precision warning and the source tools for each ID. The description adds no parameter-level detail, so the baseline 3 is appropriate.

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 ("Get metadata of an email") and enumerates exactly which fields are returned (subject, sender, recipients, times, size, status, flag, attachment flags, summary). This is clear, but it never explicitly distinguishes itself from adjacent siblings like zoho_get_email_headers, zoho_get_email_content, or zoho_get_original_message, leaving the agent to infer the boundary from the field list alone.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The agent must infer that this is the lightweight metadata lookup versus content/header siblings purely from the enumerated fields, with no explicit routing statement.

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