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

Annotations already establish the read-only, idempotent, non-destructive nature. The description adds value by disclosing the expected return contents (name, address, services, quality ratings), which is useful because there is no output schema. It does not mention rate limits or auth, but for a simple read-only search tool this is acceptable.

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 two short sentences with no filler. It front-loads the core action and resource, then quickly lists the useful output fields. Every word earns its place.

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 optional-parameter search tool, the description is complete: it names the source dataset, the target population, and the return fields. The input schema covers filtering and pagination parameters, and the annotations cover safety and idempotency, so nothing critical is missing.

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?

All four parameters have descriptions in the input schema, so the schema carries full parameter documentation. The tool description adds no additional parameter-level meaning beyond the general search domain, which matches the baseline score of 3.

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 uses a specific verb ('Search') and a specific resource ('Medicare-certified home health agencies from CMS Home Health Compare'), and it names the returned data types: agency name, address, services offered, and quality ratings. This clearly distinguishes it from sibling tools like cms_hospital_search or cms_nursing_home_search.

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 clearly establishes when this tool is relevant: whenever the user needs Medicare-certified home health agencies from the CMS Home Health Compare dataset. It does not explicitly name sibling alternatives or state when not to use it, so it stops short of a 5, but the context is unambiguous.

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