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

No annotations are provided, so the description carries the full burden. It usefully discloses the data source (ODS directory) and a cost of 1 credit, which is real operational context. It does not say whether the call is read-only (implied), whether results are paginated, what the default result count is, or what happens when all filters are omitted.

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?

A single front-loaded sentence with the resource first and the qualifiers after; the credit cost is tucked into parentheses so it doesn't obstruct scanning. No filler, though the fragmentary construction (no leading verb) slightly weakens immediate legibility.

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 simple four-optional-parameter lookup tool with no annotations and no output schema, the description covers what the tool is and where the data comes from. It leaves gaps an agent would care about: default behaviour with zero parameters, expected result volume, and response shape.

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 nominally 100%, but the schema descriptions are bare type stubs ('string', 'number'), so the baseline of 3 applies. The description confirms name, postcode and role as search dimensions, which helps map intent to parameters, but adds nothing about the 'limit' parameter or about partial-match vs exact-match behaviour for name/postcode.

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 names the resource precisely — NHS organisations from the ODS directory — and enumerates the entity subtypes (trusts, GP practices, pharmacies, hospitals) plus lookup keys (name, postcode, role). The verb is only implied (a noun phrase rather than 'Search...'), but the intent is unambiguous and clearly distinguishable from siblings like cqc_search or postcode_lookup.

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?

Usage is implied rather than stated: an agent can infer this is the tool for finding NHS bodies by name/postcode/role. However, there is no explicit when-to-use guidance, no mention of how it differs from cqc_search, cqc_location, or postcode_lookup, and no statement about combining or prioritising the filters.

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