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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds the 'redacted' detail, signaling that returned content is masked. It does not explain what is redacted or how request_id affects the response, but the annotation coverage lowers the burden.

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 single sentence is efficient and front-loads the key operation and the redaction trait. It is appropriately short, though it adds only the word 'redacted' beyond the title.

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 read operation with strong safety annotations, this is minimally adequate: an agent can infer that id is the draft ID and that the call is safe. But without parameter semantics, sibling differentiation, or output formatting, it leaves meaningful gaps for an agent deciding between read, preview, and history.

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?

The input schema's parameters are bare (id, request_id) with 0% description coverage, and the description does not clarify what these identify or how they relate. Little semantic value is added beyond the parameter names.

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 verb 'Read' and resource 'redacted candidate email draft' specify the operation clearly. However, it does not explicitly distinguish itself from sibling tools like email_drafts_preview or email_drafts_history, so some inference is required.

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 gives no guidance on when to use this tool rather than email_drafts_list, email_drafts_preview, or email_drafts_history. No exclusions, prerequisites, or alternative routing are provided.

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