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

The description notes the data source, refresh frequency, and cost, which are useful. However, it lacks details on pagination, authentication, rate limits, or how parameters combine. With no annotations, more behavioral context would be beneficial.

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 extremely concise: three sentences front-loading the core action, source, and cost. No fluff, every sentence provides value.

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 optional parameters and no output schema, the description should cover pagination (limit/offset) and combination logic. It mentions only a subset of parameters, leaving critical usage details unexplained.

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 maps to 4 of 7 parameters (state, city, zip, rating), adding meaning beyond the schema. However, it omits limit and offset, and does not explain parameter interaction. Schema coverage is 0%, so description partially compensates.

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 searches hospice quality data by location or star rating, and it answers a specific business question. It implicitly differentiates from sibling tools like carecompare_hospice_byCcn which is for lookup by CCN.

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 gives context (search by location/rating) but does not explicitly state when to use this tool versus alternatives like the CCN lookup. No exclusion criteria or prerequisites are mentioned.

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