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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value the annotations cannot: it discloses that results include the matching J-code and each task's Precedent H budget phase, which tells the agent what it actually gets back from a reference lookup.

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 dense sentence that is front-loaded with the verb and the resource, with no filler. It is long and comma-heavy, but every clause (scope, code families, return content) earns its place.

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?

There is no output schema, so the description must carry the return-value burden, and it does so partially by naming the J-code match and the Precedent H budget phase. Coverage is adequate for a small, bounded catalog lookup; only minor details such as result shape or ordering are absent.

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 coverage is 100%, so the baseline is 3, but the description goes further by spelling out what the query string can be (a code such as 'T19'/'JK10'/'A5' or work done such as 'trial bundle') and by mapping the five code families to the kinds enum. It meaningfully enriches the parameter beyond the schema text.

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?

Names a specific verb (finds/looks up) and a specific resource (electronic bill of costs codes under Precedent S, PD 47 Schedule 2), and enumerates exactly which code families are covered (P1-P15, T1-T41, A1-A10, X1-X15, J-codes). This is a registry/lookup tool, clearly distinguishable from the sibling calculators and the search helper, so an agent can route to it without opening the schema.

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 implies two usage modes (search by code or by work-done description) but never states when this tool is preferred over siblings or when it is not applicable. No prerequisites, exclusions, or named alternatives are given, so the guidance is only implied.

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