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

With no annotations provided, the description carries the full behavioral burden, and it does disclose important behaviors: unpaid requests return HTTP 402, a valid X-PAYMENT causes the same URL to return JSON, and newer-than-watermark requests can yield an empty set (304 or recordCount 0 as noted in the schema). It does not cover retry semantics, rate limits, or response structure beyond 'JSON', but the key payment gate and output behavior are transparent.

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 compact and front-loads the endpoint and cost before explaining chunking variants. Every major behavior is stated in a small space. Some phrasing, especially 'Not a new SKU,' is cryptic and may not earn its place, but the overall structure is efficient and scannable.

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 fetch tool with no output schema, the description explains the payment precondition, the 402 error, and the fact that JSON is returned after valid payment, while the input schema documents all five parameters. It does not describe the JSON response shape or pagination edge cases beyond the schema, which is a gap, but the tool is still usable by an agent that understands payment and URL semantics.

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 input schema already provides 100% coverage with meaningful descriptions for id, page, since, before, and x_payment, so the description adds little parameter-level detail beyond pricing context. It repeats the ?id/?before/?since patterns without elaborating on formats or edge cases, so the schema remains the primary source of parameter meaning.

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 identifies the resource (STB Board Decision/Order text served at ticks.bnm.farm/stb-decisions) and explains the main retrieval modes: a plain GET for the newest chunk, ?id for one official text, and ?before/?since for older/newer chunks. It does not explicitly contrast with sibling tools, but the endpoint and resource description are specific enough for an agent to understand what this tool does.

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 concrete selection rules: plain GET for newest chunk, ?before for older chunk, ?since for newer-than-watermark, and ?id for one official text. It also explains the payment precondition, the 402 on unpaid requests, and that a valid X-PAYMENT unlocks JSON. It does not name sibling alternatives or provide a 'when not to use' rule, but the usage contexts are explicit and operational.

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