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

With no annotations supplied, the description carries the full burden and does add two genuinely useful facts: a Bearer API key is required, and email content is untrusted external material (a prompt-injection warning). However, it omits key behavioral traits for an inbox tool — whether listing marks messages as read, how paging behaves, and that the operation is a non-mutating read.

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?

Three short sentences, front-loaded with the operation, followed by the prerequisite and the safety caveat. Nothing is wasted and no sentence is 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?

The description covers the operation, auth requirement, and a safety caveat, which is more than many peers manage. But with 0% schema coverage and no output schema, the absence of any return-shape or parameter guidance leaves real gaps for a four-parameter listing tool.

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 0% and there are four parameters (limit, folder, offset, search) whose meanings and constraints are documented nowhere beyond bare defaults. The description adds no information about filtering, paging semantics, or what folder values are valid, so the agent must infer all of this.

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?

"List incoming messages" gives a specific verb (List) and resource (incoming messages), which cleanly separates it from single-message siblings like get_email and from list_proposals. It stops short of naming those siblings explicitly, so the differentiation is inferable 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?

The verb "List" implies you call this to survey the inbox before fetching a specific message with get_email, but the description never says when to use it, when not to, or which sibling to prefer for a narrower slice. Usage is implied by the name rather than guided by the text.

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