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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds significant behavioral context beyond that: it discloses the cost per call ('$0.10 USDC per call'), the source ('Stratalize AI citation composite'), and the nature of the output (citation-based). It does not mention rate limits or error handling, but given the read-only nature, this is a strong addition.

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 informative and front-loaded with the usage trigger ('Use when...'). It packs a lot of value into a few sentences: use case, output, example, source, and cost. It is not overly verbose, though the example takes up space. The structure is logical and efficient, earning a high but not perfect score.

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 simple tool with one required parameter and no output schema, the description provides most necessary context: purpose, output content, example, source, and cost. It does not explain the output format (though no output schema exists) or error cases. Given the annotations cover safety, the description is nearly complete. Minor gaps keep it from a 5.

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 coverage is 0%, and the description does not explain the 'category' parameter at all. It gives an example ('EHR category') but does not define acceptable values, format, or whether it's a free-text or enumerated list. The agent must infer what 'category' means from the description's context, which is insufficient for a parameter that is the sole required input. The description fails to compensate for the missing schema documentation.

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 a specific use case: 'researching which vendors dominate AI recommendations in a healthcare technology category or validating a health IT vendor selection.' It names the exact output: top recommended vendors, AI consensus narrative, and sample size. The example with EHR category illustrates the kind of data returned. This differentiates it from generic sibling tools like get_category_ai_leaders by emphasizing healthcare-specific citation analysis and the Stratalize source.

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?

It explicitly states when to use: 'Use when researching which vendors dominate AI recommendations in a healthcare technology category or validating a health IT vendor selection.' This gives clear context but does not mention alternatives or when not to use it, though the healthcare specificity implies a boundary. It stops short of naming sibling tools, so it's not a full exclusion set.

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