open_payments_summary

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

The readOnlyHint annotation covers the safety profile, and the description adds useful context about the national scope and all-years aggregation. However, it does not disclose other behavioral traits such as the data source, years available, or any limitations. The bar is lower due to the annotation, but more detail could improve transparency.

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 two sentences, front-loaded with the core purpose and followed by a plain-language elaboration. Every word earns its place, with no unnecessary detail or repetition.

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 parameterless, read-only summary tool, the description is largely complete: it states what the tool does and what it returns (totals and averages across all years). It could mention the dataset timeframe or that it is a national aggregation, but given the tool's simplicity and annotations, it is sufficiently contextual.

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?

With zero parameters, the schema already fully covers parameter semantics (baseline 4). The description adds meaning by explaining the output scope, which is appropriate even though no parameters exist.

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 states a specific verb ('Get') and resource ('national-level Open Payment totals and averages across all years'), clearly distinguishing it from sibling tools like open_payments_by_physician or open_payments_by_company. The second sentence adds a concise explanation of the real-world meaning ('how much money flows from pharma to doctors nationally').

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 implies usage by highlighting 'national-level' and 'across all years', but it does not explicitly state when to use this tool versus alternatives (e.g., open_payments_by_physician for physician-level data). There are no direct exclusions or alternative names given, so the guidance is implied rather than explicit.

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