health.hospital-lookup

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

Without annotations, the description carries the burden of transparency. It lists return fields but omits potential behavioral aspects like pagination (limit/offset), rate limits, or data freshness. It does not contradict any annotations since none are provided.

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, consisting of two front-loaded sentences. The first covers purpose and usage, the second lists outputs, with no redundant 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?

Given the absence of annotations and output schema, the description is fairly complete, covering purpose, usage, and return fields. It lacks details on pagination and error handling but is adequate for a lookup tool.

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 low (25%), and the description adds meaning by explaining search modes (facilityId for exact, name/city/state/hospitalType/minRating for fuzzy). However, it does not elaborate on each parameter's format or constraints, leaving some gaps.

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 does a CMS Care Compare hospital lookup, with specific lookup methods (by facility ID or fuzzy search) and explicit return fields. It distinguishes from sibling tools like health.hospital-quality by focusing on general hospital information.

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 explains when to use exact facility ID lookup versus fuzzy search with optional filters, providing implicit usage guidance. While it does not explicitly state when not to use or mention alternatives, the guidance is clear enough for an AI agent.

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