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

Annotations only declare readOnlyHint=false, openWorldHint=false, destructiveHint=false, which conveys little about content; the description adds meaningful behavior beyond them: the result is bounded, includes verification time and provenance, comes from a monitored GOV.UK source, and the call is Free. It still omits rate limits or failure behavior, but for a single-read evidence tool this is solid added context.

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?

One dense but well front-loaded sentence; the use condition leads and the return contents and cost follow. The trailing "Free." fragment is terse but earns its place as a cost signal.

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?

An output schema exists, so explaining return values is optional and the description still does so helpfully. The real gap is the undocumented required source_id and no pointer to the sibling tool that would supply it, which an agent needs in order to call this successfully.

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 for the single parameter is 0% and the description never mentions source_id, its format, or where an agent obtains a valid value (e.g., from list_guidance_sources). With low coverage the description is expected to compensate, and it does not.

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 (verification evidence from a monitored GOV.UK employment source) and enumerates what comes back: source identity, verification time, provenance, and a bounded excerpt. It is clear what the tool retrieves, though the verb is implied by the name rather than stated, and it does not explicitly distinguish itself from siblings like get_capability or list_guidance_sources.

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?

"Use when an agent needs evidence for a consequential answer" gives a concrete triggering condition tied to answer stakes. It does not, however, state when NOT to use it or name an alternative tool for less consequential lookups.

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