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

Annotations only cover generic flags (readOnlyHint=false, idempotentHint=false, openWorldHint=true). The description adds crucial asynchronous semantics: the call returns before provider completion and success must be confirmed via get_mail_action, plus a retry/idempotency constraint. This is exactly the context annotations cannot express.

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 tight sentences, front-loaded with purpose before the async caveat and the retry rule. Slight wording slip: 'Never retry an uncertain send' reuses 'send' terminology that reads oddly for a read-status operation.

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 mutating, non-idempotent tool with no output schema, the description supplies the important operational context: fire-and-poll behavior, the confirming tool, and idempotency-key reuse. It leaves accountId semantics and the exact meaning of isRead unstated, but nothing critical for invocation is missing.

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%: messageId and operationId carry rich descriptions, while accountId and isRead are undocumented. The description partly compensates by linking operationId to the polling step and implying the read-state target, but it never clarifies accountId or the semantics of isRead explicitly.

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 ('Set the read state of a message'), which is clearly distinct from siblings like set_email_starred or move_email. It doesn't explicitly name an alternative, but the purpose is unambiguous.

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?

Gives concrete operating guidance: the return is only a queued operation, poll get_mail_action with the operationId, and do not retry with a fresh operationId. It names the follow-up tool and the retry condition, though it does not contrast this tool against alternatives for other state changes.

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