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

The readOnlyHint/openWorldHint annotations already cover the safety profile, and the description adds genuinely non-obvious behavior: a per-call price of $0.002 USDC charged via x402 on Base, Solana or Arc, with failed calls not charged. That billing/monetization detail is exactly the kind of trait an agent cannot infer from structured fields. It stops short of noting rate limits or result caps beyond 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?

A single dense paragraph that front-loads the dataset identity, then coverage, then filters, then price. No filler sentences, and the cost disclosure is placed last where it belongs.

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?

With an output schema present, the return-field enumeration is partly redundant, but the description still carries scope, year range, filter surface and the payment model. For an 8-parameter read-only lookup this is essentially complete; only filter-combination semantics are missing.

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 description coverage is 100%, so every one of the 8 parameters is already documented with examples and defaults. The description restates the filterable dimensions but adds no syntax, matching behavior (e.g. prefix vs exact for company/product), or interaction between filters. Baseline 3 is appropriate.

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 exact dataset (CMS Open Payments / Sunshine Act general payments) and the entities it covers (drug and device makers to US physicians, prescribers and teaching hospitals), which no sibling tool overlaps with. It reads as a data-retrieval tool rather than an explicit verb, but the resource and scope are unmistakable.

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 implies when the tool applies by enumerating available filters (company, last name, NPI, state, product) and the program-year range, but never states when to prefer it over a sibling or what combinations are invalid. No exclusions, no prerequisites, no guidance for zero-result or pagination situations.

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