find_hospitals

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

No annotations are provided, so the description carries full burden. It only states the basic purpose without disclosing behavioral traits such as number of results, ordering, error handling, or authentication requirements. This is minimal transparency.

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 very concise (one sentence plus parameter list) and front-loads the purpose. No wasted words, though it could be slightly more structured (e.g., noting 'UK postcode').

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 tool is simple (1 parameter) and has an output schema, the description is adequate but incomplete. It lacks details like postcode format variations (e.g., case sensitivity, spaces) and result limits, which could affect agent behavior.

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 0%, but the description adds value by specifying 'UK postcode', clarifying the expected format beyond the schema's generic 'string' type. This helps agents understand what input is valid.

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 'Find hospitals near a postcode' with a specific verb (find) and resource (hospitals) and context (near a postcode). It distinguishes from siblings like find_gp_surgeries and find_pharmacies, which are different services.

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?

There is no guidance on when to use this tool versus alternatives. With many sibling tools for similar location-based services (e.g., find_gp_surgeries, find_pharmacies), the description lacks any context about selection criteria or when to prefer this tool.

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