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

The description discloses the crucial non-obvious behavior: a $0.10 per-call charge, the USDC-on-Solana x402 payment protocol, and the exact challenge-then-retry mechanics including the _meta["x402/payment"] key. This explains why idempotentHint and readOnlyHint are false despite the operation being a read — the payment step is the state change — and is far beyond what the annotations convey alone.

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?

Two dense sentences, front-loaded with the purpose before the payment mechanics. The payment detail is essential rather than padding, though the HTTP-equivalent tail is somewhat secondary for an MCP caller.

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 single-parameter lookup with no output schema, the definition covers the inputs, cost, and payment flow thoroughly. The only gap is that it does not characterize what 'full case detail' returns (fields, prosecution history, status), which an agent might want before paying $0.10.

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% and the single parameter is documented as an '8-digit USPTO serial number'. The description adds only that it appears as {serialNumber} in the HTTP path, so the baseline 3 applies — the schema does the semantic work.

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?

States a specific verb and resource — 'Fetch full case detail for a trademark serial' — which is clearly distinct from trademarks_search (list/find) and trademarks_watch (subscription). It stops short of naming the sibling tools explicitly, so the differentiation is inferable from the name rather than stated.

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?

Usage is only implied: an agent must infer that trademarks_search finds the serial and this tool then returns detail. There is no explicit when-to-use/when-not guidance and no mention of the watch siblings that might be the better choice for ongoing tracking.

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