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

With no annotations, the description carries the behavioral burden and does disclose key traits: payment to a specific address, HTTP 402 when unpaid, X-PAYMENT header required for JSON, pricing per mode, and chunk/watermark behavior. It does not describe response structure beyond 'returns JSON', and 'Not a new SKU' is cryptic, but most operational behavior is 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 dense but mostly purposeful, packing endpoint, cost, payment flow, and pagination into four sentences. However, the opening mixes URL, price, and wallet address in one long breath, and the final 'Not a new SKU' is unexplained and likely to confuse rather than inform.

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?

Given five parameters and no output schema, the description covers parameter behavior, payment requirements, and chunk pagination well. It lacks any indication of the JSON response shape, which makes it harder for an agent to know how to consume the result, and the SKU comment remains unresolved.

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 describes all five parameters with 100% coverage, so the baseline is 3. The description adds pricing and clarifies some relationships ('Omit for the newest chunk', 'Same door, not a new SKU'), but it does not substantially extend the schema's 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 identifies the resource as 'USDA FSIS humane-handling enforcement letter text' and the endpoint as GET https://ticks.bnm.farm/fsis-humane, distinguishing it from sibling letter tools. The core purpose is clear, but the message is cluttered with pricing and payment details and lacks a crisp verb like 'fetch' or 'retrieve'.

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?

There is no explicit guidance about when to use this tool versus alternatives, and the large sibling list contains related tools like search, get-page, and other letter endpoints. The description only defines pagination/billing modes ('Newest chunk on a plain GET', 'older chunk if they ask'), not when this tool is the right choice.

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