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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds the central behavioral trait absent from annotations: results are sorted descending by payment amount, and the tool inherits the search filter behavior. No contradictions with annotations.

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 short sentences with the distinguishing sort behavior stated first and the recommended use case second. No filler, no redundant restatement of schema fields, and every sentence earns its place.

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 tool with six optional filters and no output schema, the description provides key selection context: same filters as open_payments_search and sorting by payment amount descending. It does not spell out return fields or pagination behavior, but the schema and sibling tool reference cover enough for an agent to invoke it correctly.

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?

All six parameters have individual descriptions in the input schema, so schema coverage is 100% and the schema carries the parameter semantics. The description only adds high-level filter categories and references open_payments_search's filters, without adding per-parameter meaning. 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 clearly states a specific operation: return Open Payments data with the same filters as open_payments_search, sorted by payment amount descending. It names the reference sibling and frames the tool's purpose as finding the largest individual pharma payments. This distinguishes it well from open_payments_search and other open_payments variants.

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 a concrete use case: use this tool to find the largest individual pharma payments by company, state, or specialty. It does not explicitly list exclusions or when to prefer open_payments_search over this tool, but the usage context is clear enough for an agent to select it appropriately.

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