gmail_read

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' correctly signals a non-mutating operation, but it is silent on whether fetching marks the message as read in Gmail, what content format is returned (plain/HTML/headers/attachments), or any auth requirement — all traits an agent would want before calling.

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?

One sentence, front-loaded with the verb and resource, zero filler. Nothing to trim and nothing essential buried.

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 one-parameter read tool with a fully documented schema and no output schema, the definition is nearly sufficient. The remaining gap is return-shape expectation: 'full content' hints at a body but doesn't say which fields come back, which matters somewhat absent an output 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 coverage is 100% and the single parameter is fully documented, including its provenance ('from gmail_search results'). The description's 'by its message ID' adds nothing beyond the schema, 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?

Specific verb+resource: 'Read the full content of an email', which clearly separates it from gmail_search (which finds messages) and gmail_send/gmail_reply (which write). The 'full content' vs. search-results distinction is useful, but it never names the sibling it complements, so differentiation is implied 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?

'by its message ID' implies the prerequisite — you must already have an ID, presumably from gmail_search — but the description never states when to use this instead of, say, listing or searching. The usage pattern is inferable from the single required parameter, not from explicit guidance.

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