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

Annotations already declare destructiveHint=false and openWorldHint=false, and the description usefully adds cost ('Free') and output scope. However, readOnlyHint=false is at odds with the purely informational framing ('Returns current preserved verification status'), and the description never explains what the non-read-only aspect is, nor mentions caching or rate limits on the freshness check.

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?

Two sentences, both load-bearing: one for when to call, one for what comes back plus cost. It is front-loaded with the trigger condition and contains no filler or restatement of the tool name.

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 return-value detail is legitimately omitted, and the description covers timing, scope and cost for a one-optional-parameter tool. The remaining gaps are the ID format for source_id and the unexplained non-read-only annotation, both minor.

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 0% and the single parameter is a bare string with an empty default, so the description carries the burden. It does add real meaning by saying the call covers 'one or all monitored sources', implying source_id is an optional filter, but it gives no hint about the expected ID format or where to obtain valid IDs.

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 second sentence states a specific verb and resource: returns verification status, freshness and provenance for monitored guidance sources, scoped to 'one or all'. That is concrete enough to distinguish it from siblings like get_guidance_changes or list_guidance_sources, though it never names or contrasts those siblings explicitly.

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 before answering or acting when current official GOV.UK employment guidance materially matters' gives a clear triggering condition, which is unusually good for a status tool. It stops short of naming when-not-to-use or pointing to an alternative (e.g. get_verification_evidence for deeper evidence), so it is not a full 5.

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