open_payments_top

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

Annotations declare readOnlyHint=true, so there is no contradiction. The description adds behavioral context by specifying 'sorted by amount descending' and noting it differs from 'basic search which returns results in default order', going 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?

Three sentences, front-loaded with the main purpose, no filler or redundant information. Every sentence contributes to understanding or differentiation.

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?

The tool is simple with 6 optional params and readOnly annotation. Description covers purpose, use case, and sorting behavior, but lacks details on return format or pagination; however, given no output schema and clear intent, 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 covers 100% of parameters, so baseline 3 applies. The description references 'state or specialty' filters but does not add new semantic details beyond the schema descriptions.

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?

Description states 'Find the HIGHEST pharma payments to doctors — sorted by amount descending', providing a specific verb, resource, and ordering. It also contrasts with 'basic search' which distinguishes it from sibling 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?

Gives explicit use case: 'Use this to find the biggest consulting fees, royalties, and speaking fees in a state or specialty.' It also mentions the alternative 'basic search' for default order, offering clear context on when to use this tool.

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