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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, auth requirements, rate limits, or side effects. It implies a read operation but fails to explicitly state so, leaving a significant gap for the agent.

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 concise with two sentences plus source and price. It is front-loaded with the core purpose. However, the price tag, while potentially useful, is arguably extraneous and slightly reduces conciseness.

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?

Given no output schema, the description explains the tool returns 'quality ratings and performance measures', which gives a general idea but lacks detail on structure. For a simple parameter set, it is adequate but not 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?

The input schema has 100% coverage, describing the single parameter 'ccn' as 'Path parameter: CMS Certification Number'. The description adds no additional meaning beyond reiterating 'by CCN', so it meets the baseline without exceeding it.

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 retrieves CMS Care Compare quality record by CCN for home health, answering quality ratings and performance measures. It distinguishes from sibling tools by specifying 'home health' and 'by CCN', implying others are for different facility types or endpoints.

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 implicitly suggests using this tool when you have a CCN for a home health facility, but does not explicitly state when to use it versus alternatives like carecompare_home-health_search or other facility-specific tools. No exclusions or when-not guidance provided.

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