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

Annotations already cover safety (read-only, idempotent, non-destructive). The description adds useful behavioral context beyond annotations: the output is full text of numbered recommendation paragraphs, including conditions around marketing authorisation and commercial arrangements. It does not describe error behavior, but the openWorldHint mitigates that need.

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 moderately detailed but each sentence adds value: it defines the content, the conditions included, and the core question answered. It could be slightly tighter, but it is well-structured and front-loads the primary purpose.

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 single-parameter, read-only retrieval tool with no output schema, the description is complete: it specifies what the returned text contains, the scope, and the practical relevance. An agent has enough information to invoke the tool correctly and interpret the result.

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?

There is only one parameter, and the input schema already documents it fully with an example ('TA1040'). The description adds little beyond connecting the id to NICE guidance, so a baseline score of 3 is appropriate since the schema carries the explanatory burden.

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 identifies the resource: the recommendations chapter of NICE guidance, and states the exact question it answers ('did NICE recommend this treatment, and for whom'). It also differentiates itself from the sibling nice_guidance by specifying it returns the recommendations chapter rather than the full guidance.

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 a clear context for when to use the tool: when the agent needs the recommendation wording that decides NHS funding. It does not explicitly name alternatives or state when not to use it, but the context is strong enough to guide selection among NICE-related siblings.

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