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

No annotations are provided, so the description must cover behavioral aspects. It states the tool returns quality records, ratings, and performance measures, implying read-only behavior. It transparently mentions the price ($0.01/call). However, it does not disclose error handling, rate limits, or what happens if the CCN is invalid. The description is adequate for a simple read tool but lacks depth.

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, consisting of one sentence and two lines for source and price. It is front-loaded with the core purpose. The price note is relevant but could be integrated more seamlessly. Every sentence serves a purpose, though the sentence could be more structured (e.g., 'Retrieves quality ratings and performance measures for a hospital by its CMS Certification Number').

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 the tool's simplicity (one parameter, no output schema, no nested objects), the description adequately covers the main purpose and the nature of the response (quality ratings and performance measures). It also notes the data source and cost. While it could detail the specific measures returned, the lack of an output schema reduces the burden. The description is sufficient for an AI agent to select and invoke this 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?

The schema has 100% coverage with a clear description for the single parameter 'ccn' ('Path parameter: CMS Certification Number'). The description adds context by stating the tool is 'by CCN' and explains the output, but does not provide additional semantics like format, length, or examples. Baseline 3 is appropriate as the schema already documents the parameter effectively.

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 the tool retrieves quality ratings and performance measures for a hospital given its CCN. The verb is implied, and the resource is specific ('CMS Care Compare quality record'). It distinguishes from sibling tools like 'hospitals_search' by specifying it is by CCN. However, it could be more explicit about the action (e.g., 'get' or 'retrieve').

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 implies use when a CCN is available, but does not explicitly state when to use this tool versus alternatives like 'carecompare_hospitals_search' or other facility types. No exclusions or alternative recommendations are provided, relying on the user to infer from the tool naming.

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