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

No annotations provided, so description carries full burden. It describes aggregation behavior ('rolled up to paying company') and defaults, but doesn't explicitly state read-only nature or other behavioral traits. Adequate but not exceptional.

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?

Description is a single paragraph of ~80 words, front-loaded with purpose, followed by filters, sorting, and price. Every sentence is informative with no redundancy.

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?

Covers purpose, filters, sorting, and defaults despite no output schema. Missing explicit return format, but context implies columns (manufacturer, spend, physicians). Overall sufficient for a complex tool.

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 67%, and description adds meaning to parameters like max_total_spend (small/emerging) and default performance_year. It compensates for missing schema descriptions, scoring above baseline.

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 'Which manufacturers pay a given physician specialty in a territory, and how much' with specific verb 'pay' and resource. It provides examples like 'which pharma/device companies already reach cardiologists in Texas', distinguishing it from sibling tools focused on other healthcare data.

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?

Description explicitly lists filters and sort options, and shows query context. It doesn't explicitly state when not to use, but provides clear context, earning a 4.

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