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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the payment requirement ($0.05, $0.02), the HTTP 402 behavior when unpaid, and that after a valid X-PAYMENT the URL returns JSON. It also differentiates chunk retrieval semantics. Avoids contradictions and adds meaningful behavioral context beyond the URL.

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 a single dense paragraph that front-loads the URL and price, then covers chunk semantics and payment. Every sentence provides necessary information, though the phrase 'Not a new SKU' repeats the schema's 'Same door, not a new SKU'. It is appropriately concise for the complexity.

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 API with no output schema, the description should explain what the returned JSON contains, but it only says 'returns JSON' without structure or fields. It also does not describe pagination behavior beyond chunk retrieval, nor error cases beyond 402. Adequate for basic usage but leaves gaps in return format and error handling.

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%, so all four parameters have descriptions. The tool description largely reiterates the schema info (e.g., id pricing, before behavior) without adding substantial new meaning. It does clarify the payment flow tied to parameters, but that is more behavioral than semantic. Baseline 3 is appropriate.

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 immediately identifies the exact resource: 'TTB institution Offer in Compromise text' served via GET to a specific URL. It distinguishes itself from siblings by being institution-specific and explains the two retrieval modes (newest chunk vs. specific id). This is a clear verb+resource statement.

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 explains how to use the tool's parameters (plain GET, ?id=, ?before) but does not explicitly guide when to select this tool over sibling tools. It mentions 'Not a new SKU' implying it belongs to a family, but no exclusions or alternatives are named. Usage context is implied by the institution-specific purpose but not stated directly.

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