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

With no annotations, the description carries the behavioral burden. It discloses payment pricing, the x402 X-PAYMENT flow, the unpaid 402 response, the paid JSON return, and the chunking/watermark semantics. It does not mention rate limits or response structure details, but the critical payment-gated behavior is clearly exposed.

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 information-rich, but it is structured as a run-on set of clauses with repeated price mentions and the confusing 'Not a new SKU' aside. It is concise in length but could be better organized with clearer sentence boundaries or bullets.

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 there is no output schema, the description covers the essential invocation context: endpoint, auth/payment mechanism, error behavior (402), successful response type (JSON after valid X-PAYMENT), and pagination semantics. It is slightly incomplete on what the JSON payload contains for a paid text request, but for the core paid-API flow it is sufficiently complete.

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 coverage is 100%, so the baseline is 3, but the description adds significant meaning beyond the schema: cost per parameter, page-1 being the newest chunk, since/before being mutually relevant pagination controls, and the X-PAYMENT forwarding behavior. This materially helps an agent choose and fill parameters correctly.

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 names a specific resource (PHMSA pipeline enforcement-order text) and the action (GET on https://ticks.bnm.farm/phmsa-orders), making the core purpose clear. It is not a full 5 because the 'Not a new SKU' phrasing is cryptic and the description does not explicitly contrast with sibling order/report tools beyond the agency-specific name.

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 usage branches: use ?id= for one official text, a plain GET for the newest chunk, ?before= for an older chunk, and ?since= for newer-than-watermark texts. It also explains the payment requirement and HTTP 402 for unpaid requests. It lacks an explicit 'use this instead of sibling X' statement, but for a per-agency data endpoint this is adequate.

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