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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds value by disclosing the returned fields (provider name, address, ownership, quality measures), which matters since there is no output schema, though it omits pagination behavior and any rate/auth caveats.

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?

Two sentences, zero filler, with the core action and data source front-loaded before the return-field list. Every clause carries information.

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 filterable search tool with full schema coverage and safety annotations, the description supplies the one thing structured fields do not: the shape of the results. It stops short of describing result volume/pagination interaction, but nothing essential for a correct call 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?

Schema description coverage is 100% with all four parameters (limit, state, offset, name_contains) documented in the schema itself. The description adds no filter syntax, format, or combination semantics beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb (search) and resource (Medicare-certified hospice agencies) plus the data source (CMS Hospice Compare). The resource noun cleanly distinguishes it from the sibling cms_home_health_search, cms_hospital_search, and cms_nursing_home_search 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 scope (Medicare-certified hospice agencies, from CMS Hospice Compare) implies when the tool is useful, but there is no explicit when-to-use guidance, no exclusions, and no mention of how to choose between this and the parallel CMS search tools. Usage must be inferred from the resource name.

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