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

No annotations exist, so the description carries the burden. It discloses monthly data refresh and cost ($0.02/call), but does not mention any constraints like rate limits, pagination behavior, or response format. This is adequate but not rich.

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 short and front-loaded with the tool's purpose. Every sentence adds value (purpose, question, source, pricing). Could be slightly improved but is efficient.

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 7 parameters, no output schema, and no annotations, the description provides a basic understanding of input criteria but lacks details on output structure, pagination, or filtering behavior. Adequate for a simple search tool but incomplete.

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 description lists searchable fields (state, city, ZIP, rating) but does not explain each parameter in detail (e.g., zip_prefix vs full ZIP, rating_min/max semantics, limit/offset usage). With 0% schema description coverage, the description adds minimal value beyond naming the parameters.

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 searches home health quality data by state, city, ZIP, or CMS star rating, and answers a specific market question ('which home health meet quality thresholds?'). This distinguishes it from sibling tools like byCcn lookups and other specialized searches.

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 usage for location or rating-based searches but does not explicitly say when to use this tool over alternatives (e.g., byCcn for direct lookup). No when-not-to-use guidance or exclusions are provided.

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