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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds material context beyond them: 'This server signs and sends nothing' clarifies that the returned calldata is for the root's owner to send from its own wallet, and 'checked here against the pool, the offer and the consent' discloses an internal validation step. It does not say what happens when no offer has been accepted yet beyond the implied 'once'.

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 front-loaded correctly with 'Show one request on Priors' line board', but the body is a single ~110-word run-on with deeply nested parentheticals, which makes the enumeration of offer fields and calldata hard to parse. The content earns its place; the packaging does not.

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?

There is no output schema, and the description effectively supplies one by enumerating every returned component (root, owner, amount, premium, deadline, consent nonce, calldata target/function). Combined with the safety statement and the validated-against check, an agent has everything it needs to call this correctly.

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 100% and the single parameter is fully documented there, including the EIP-712 hash format and its provenance from find_line_requests. The description adds nothing about the parameter itself, so the baseline 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?

States a specific verb and resource ('Show one request on Priors' line board') and enumerates exactly what the view contains: the root offer, owner, amount, premium, deadline, the consent, and the vouchWithConsent calldata. The singular 'one request' versus the sibling find_line_requests (plural) is clear from the text itself.

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 context for use is unmistakable: an agent that already has a request_id and needs its standing offers, consent, and the exact call the root's owner must send. No explicit exclusions or named alternatives are given (line_options, priors_line_quote, stock_line_request are never mentioned), so it stops short of a 5.

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