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

With no annotations, the description carries the full burden and does disclose important runtime behavior: unpaid requests return HTTP 402, a valid X-PAYMENT causes the same URL to return JSON, and different calls cost different amounts. It doesn't describe the JSON shape or failure modes for invalid ids, but it exposes the core payment and response behavior.

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 dense and front-loaded with the endpoint and cost, and nearly every clause adds information. The telegraphic phrasing is a little jumbled, but it avoids redundancy and fits the essential payment and pagination details into a short block.

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 paid, externally hosted resource with no output schema, the description covers the URL, cost/payment address, 402 behavior, X-PAYMENT forwarding, and parameter-to-chunk semantics. It does not spell out the JSON response fields, but what an agent needs to make a correct first call is largely present.

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 schema already explains id, page, before, and x_payment in detail, so the description adds limited new semantics. It does reinforce the pricing model and the 'same URL' idea, but this stays largely at baseline rather than compensating for things the schema misses.

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 identifies a concrete resource (BIS institution charging-letter / order text at /bis-orders) and the retrieval action (GET), including id-based official text vs plain GET newest chunk. It is specific enough to distinguish from the broader order/letter siblings by institution, though it does not explicitly compare itself to them.

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?

It gives clear, actionable guidance on which request form to use: ?id= for one official text, a plain GET for the newest chunk, and ?before for an older chunk, plus X-PAYMENT for access. It does not explicitly name alternative tools or say when not to use this endpoint, but the context is not misleading and exclusions are implied by its own parameter instructions.

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