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

No annotations are provided, so the description carries the full behavioral disclosure burden. It discloses the payment gate, HTTP 402 behavior, X-PAYMENT header requirement, and the fact that the same URL returns JSON after payment. It does not explicitly state read-only/idempotent behavior, but the GET-only design and payment-before-response model make the side-effect profile reasonably clear.

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 every clause carries useful information, but it is not well front-loaded: it begins with the payment address and pricing before stating the core purpose. The heavy use of semicolons and price annotations makes it harder to parse quickly, even though there is no filler or repetition.

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 GET tool with no output schema, the description covers essentially all caller-relevant context: available request modes, pricing, payment authorization, failure behavior, and response type. It does not describe the JSON shape, but the schema covers the parameters thoroughly and the description gives enough to successfully construct and pay for a request.

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 the schema already fully documents all five parameters. The description adds useful context about pricing and which request mode maps to each parameter, but it does not materially expand the semantic meaning beyond what the input schema already provides. 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 clearly states this tool serves NLRB published Board Decision text from a specific paid GET endpointmente. It distinguishes the id-based official text lookup from chunked newest/older/newer-than-watermark requests, which gives an agent a concrete picture of what the tool does. It does not explicitly differentiate from sibling tools, but the NLRB resource and the API variant semantics are specific.

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 usage variants: plain GET for newest chunk, ?id= for one official text, ?before= for older chunks, and ?since= for newer-than-watermark. It also states that unpaid requests return HTTP 402 and that a valid X-PAYMENT is required before JSON is returned. This is strong operational guidance, though it does not compare against sibling tools directly.

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