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

No annotations are provided, so the description carries the full burden. It mentions the data source (CMS Care Compare) and cost, but fails to disclose behavioral traits such as rate limits, error handling for invalid CCNs, or whether the operation is read-only. Minimal beyond purpose.

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 one main sentence, a clarifying question, and a cost note. It is front-loaded with the core purpose. Minor improvement could separate metadata (cost) from the functional description.

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 single-parameter lookup tool with no output schema, the description adequately explains what the tool returns (quality ratings and performance measures). It is sufficiently complete for its simplicity, though it could mention output format.

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?

With 100% schema description coverage, the description adds context by clarifying that ccn is a 'CMS Certification Number,' which is already stated in the schema. The added value is marginal; it confirms the purpose but does not provide format or constraints beyond the schema.

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 a CMS Care Compare quality record for a SNF by CCN, answering specific questions about quality ratings and performance measures. It distinguishes itself from sibling search tools and other provider-type tools.

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 known and quality data is desired, but lacks explicit guidance on when to use alternatives (e.g., carecompare_snf_search). No when-not-to-use or prerequisite information is provided.

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