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

Annotations already declare readOnly=false, destructive=true, idempotent=true, and openWorld=true. The description adds useful behavioral detail beyond that: support write authority is required, dispatch is limited to the existing supported retry identity, Gmail acceptance is checked without resending, and unsupported/expired cases remain unknown.

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?

The description is short and front-loads the core purpose before adding operational constraints. Each sentence carries relevant information, though some phrasing is dense and provider-specific.

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 tool has an output schema, and annotations cover safety and idempotency hints. The description fills important gaps around authority requirements, retry identity, Gmail behavior, and unknown-result handling, though it does not explain what the destructive action may affect or when to prefer a sibling 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 100%, so all three required UUID parameters are already documented in the schema. The description does not add parameter-specific meaning, which is acceptable given the complete schema, but it also does not compensate with extra context.

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 action: reconciling original messages and repairing abandoned delivery observations. It is clear enough to identify the tool's role, but it does not explicitly distinguish itself from nearby siblings such as inbox_resolve or inbox_reply.

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 description implies usage through 'abandoned delivery observations' and adds a prerequisite ('requires support write authority'), but it does not explicitly say when to use this tool versus alternatives like inbox_resolve or general inbox tools.

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