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

No annotations provided, so the description must carry the burden. It discloses entity resolution (DBA/subsidiary merging) and the price per call. However, it does not explicitly state read-only nature, data freshness, rate limits, or other behavioral traits. Adds some value but could be more transparent.

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 a single well-structured paragraph that front-loads the main purpose and key filters. It includes a brief price note without being verbose. Two sentences at the end summarize the query intent. Concisely provides essential information.

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 11 parameters and no output schema or annotations, the description covers the tool's purpose and key filters but does not describe the output format or fields returned. It explains the entity resolution but lacks completeness for all parameters (e.g., performance_year, min_total_spend). Adequate but not fully comprehensive.

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 has 11 parameters with 55% description coverage. The description adds meaning for key parameters like name, max_total_spend, first_seen_year_min/max, specialty, state, connecting them to the small/emerging filter. However, parameters like sort, limit, offset, min_total_spend, performance_year are not mentioned, leaving gaps.

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 it discovers manufacturers from CMS Open Payments with a specific focus on emerging/small brands using filters like name, total-spend band, first appearance year, specialty, and state. It distinguishes from siblings like manufacturers_openPayments by emphasizing the small/emerging filter and entity resolution.

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 provides clear context on when to use the tool: to find small or new manufacturers paying physicians in a given specialty/state. It lists applicable filters but does not explicitly mention when not to use or provide alternatives. The implied usage is well-defined.

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