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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it discloses the $0.05 USDC payment destination, the $0.02 official-text price, HTTP 402 when unpaid, JSON after a valid X-PAYMENT, and pagination/watermark behavior. These are exactly the non-obvious traits an agent needs before calling a paid endpoint.

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 but compact; nearly every clause carries pricing, mode, or behavioral information. It is front-loaded with the endpoint and payment address. The cryptic 'Not a new SKU' and the lack of any formatting keep it from a perfect score.

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, parameterized endpoint with no output schema, the description and schema together cover endpoint, pricing, payment address, X-PAYMENT, pagination modes, watermark behavior, and HTTP status codes. The main gap is the absence of an example or a precise statement of the JSON response fields, though the schema hints at recordCount.

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?

The schema already provides 100% rich parameter coverage, so the baseline is 3. The description adds value beyond the schema by explicitly mapping parameter choices to costs and response modes, and by naming the payment address and X-PAYMENT success outcome. This compensates for any ambiguity in the schema's brief x_payment note.

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 opens with the exact GET endpoint and identifies the resource as NCUA institution consent C&D text. It further distinguishes behavior: a plain GET returns the newest chunk and ?id returns one official text, so an agent can tell this is a retrieval tool for NCUA orders among many agency-order siblings.

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 gives explicit operational guidance: plain GET for the newest chunk, ?before for an older chunk, ?since for newer-than-watermark content, and ?id for one official text. It also states the payment and HTTP 402 behavior. It does not explicitly name sibling alternatives, but the NCUA-specific scope and query-mode rules provide clear usage context.

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