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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of the returned payload — provenance per value, replaced values, open questions, unread words, send status, and any offer — which is important since no output schema exists. It stops short of mentioning authorization beyond the private token or behavior when the requirement was never sent.

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?

It is a single front-loaded sentence with no filler, which is good. However, the colon-list is dense with domain jargon ('Groundtruth', 'words not yet read', 'any offer on it') that costs more parsing effort than a plainer phrasing would.

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?

With three fully documented parameters and no output schema, the main obligation is to say what comes back, and the description roughly does. It leaves gaps around error cases, what 'words not yet read' actually means, and how the offer portion relates to inspect_offer, which matters for a tool this data-rich.

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%, and the schema already explains all three parameters, including that slug comes from list_propositions, id comes from an earlier answer, and token is the receipt token. The description adds no further parameter guidance, so the baseline of 3 applies.

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 names the resource (a Groundtruth requirement) and the scope ('as it stands', i.e. the current snapshot), and enumerates what that snapshot contains: values, provenance, prior values, open questions, unread words, send status, and offers. The retrieval verb is only implied (carried by the name and title rather than the sentence), and nothing distinguishes it from siblings such as edit_requirement, interpret_requirement, or send_requirement.

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 explicit when-to-use statement and no mention of alternatives or prerequisites. An agent must infer from the read-only framing that this is the retrieval counterpart to edit_requirement/send_requirement, but that routing is never stated.

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