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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds behavior beyond annotations by stating the scope ('for England'), the programs searched, and the exact return fields (reference number, title, guidance type, publication date, summary). No contradictions exist.

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 front-loaded with the main action and resource, and the three sentences are substantive. The listing of guidance types is slightly redundant with the schema but not wasteful. Every sentence earns its place including the practical funding-context sentence.

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?

With no output schema, the description appropriately explains return values (reference number, title, guidance type, publication date, summary) and the semantic purpose of the search. It also gives context about the funding question. It does not mention sorting, pagination, or no-result behavior, but those are partially covered by the input schema and are less critical for a read-only search 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 100%, so the schema already documents all five parameters and the exact allowed values for guidance_type. The description adds little about parameters beyond restating that the query is a drug, device, procedure, or condition. This meets the baseline for high schema coverage but does not go beyond it.

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 uses a specific verb ('Search') and names the exact resource ('NICE guidance for England') plus the search dimensions (drug, device, procedure, condition). It also lists what is returned, making the tool's function clear. It does not explicitly differentiate from sibling NICE tools like nice_guidance or nice_recent_guidance, but the search-by-clinical-term framing is distinct enough.

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 clear usage context: it answers whether NICE has assessed a treatment and which document says so, and frames this as the first step to determining NHS England funding. It does not explicitly say when not to use this tool or name alternatives, but the intended use case is well conveyed.

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