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

Annotations already cover safety as read-only/non-destructive. The description adds operational behavior beyond that: it 'degrades per-section on source_unavailable' and discloses a $3.00 USDC cost. These are meaningful, non-schema behavioral details that an agent should know before invoking.

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 with no filler. The use case is front-loaded, followed by the data components, required inputs, and pricing. Every sentence adds actionable 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?

Covers use case, what data is synthesized, degradation behavior, pricing, and required inputs. However, there is no output schema and the description does not indicate the return format (e.g., a structured report, JSON sections), nor does it explain the meaning or constraints of the optional parameters. For a tool with six parameters and no output schema, these are clear gaps.

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 0%, so the description carries the full burden of explaining parameters. It only names vendor_name and bed_size as required, which the schema already states, and offers no semantic detail about bed_size (units, definition), nor any clarification of optional parameters (state, category, payer_name, company_name) or their filtering role.

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 purpose ('diligencing a healthcare vendor or GPO relationship') and enumerates the fused data domains (healthcare vendor market rate, GPO contract benchmark, FDA recall history, payer intelligence, hospital supply chain benchmark). This distinguishes it from single-domain siblings like get_healthcare_vendor_market_rate or get_payer_intelligence, though it does not explicitly name alternatives.

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?

Provides an explicit 'Use when...' condition that frames the tool as a comprehensive diligence option. The list of integrated sources implies that if only one sub-benchmark is needed, a targeted sibling would be more appropriate, but no exclusions or alternatives are explicitly stated.

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