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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. What the description adds beyond them is the returned content — provenance of each value, what it replaced, the open question, unread words, sent status and offers — which is genuinely useful given there is no output schema. It stops short of describing failure behavior for an unknown id or a bad token.

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?

A single front-loaded sentence enumerating the returned fields with no filler. A few phrases ('words not yet read', 'any offer on it') are domain-cryptic but compact rather than wasteful.

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 two-parameter read tool with no output schema, the description carries the return-value burden well by listing what the snapshot includes. Missing only edge-case behavior (invalid id, expired token) and any pointer to the mutation siblings.

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%, with both parameters documented (the id 'from an earlier answer' and the private receipt token). The description adds no meaning about the parameters beyond what the schema already says, so the baseline 3 is correct.

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 title supplies the verb ('Read a requirement as it stands') and the description names the exact resource plus the shape of what comes back (values with provenance, replacements, open question, unread words, sent status, offers). It is clearly a read of a single requirement rather than a mutation like edit_requirement or send_requirement, though the description alone never states the verb 'retrieve' and relies on the title to do so.

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?

There is no guidance on when to call this versus siblings such as edit_requirement, interpret_requirement, or state_purchasing_requirements, and no stated prerequisite beyond the token. The agent must infer that this is the inspection step before editing or interpreting.

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