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

With no annotations, the description carries the full burden. It transparently discloses payment requirements ($0.05 USDC on Base), the recipient address, the HTTP 402 unpaid behavior, and that a valid X-PAYMENT makes the same URL return JSON. This is valuable auth/error/response context beyond anything in the schema.

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 not padded, but it is a run-on with payment details and endpoint URL front-loaded before a clear purpose statement. Phrases like 'Same door, not a new SKU' and the awkward 'text GET ?id= is one official text' make it harder to parse than necessary.

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 x402 retrieval tool with no annotations and no output schema, the description gives the essential operational contract: endpoint, pricing, payment auth, 402 error, and JSON response. The main omission is the shape of the returned JSON, but that is not strictly needed to invoke the tool correctly given the schema.

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 documents all four parameters at 100% coverage, so the description is not required to compensate. It does add operational pricing context and clarifies chunk semantics, but much of this is also repeated in the parameter descriptions themselves.

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 the resource, 'PHMSA pipeline enforcement-order text', and the action GET, and gives the exact endpoint URL. An agent can infer it retrieves PHMSA enforcement order content, though the phrasing is grammatically awkward and relies partly on the tool name to distinguish it from sibling order tools.

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?

It gives clear usage context: plain GET returns the newest chunk, '?id=' returns one official text, and '?before=' returns an older chunk. However, it never names an alternative tool or states when to choose phmsa-orders over a sibling like search, get-one, or another agency-specific orders tool.

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