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

Annotations declare openWorldHint=false and destructiveHint=false, so the safe/closed-world profile is already covered. The description usefully adds "Free" and the scope boundary, but it never addresses the odd readOnlyHint=false annotation (a listing call that the server flags as not read-only), which is exactly the kind of behavior an agent would want clarified.

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?

Three short sentences, front-loaded with the usage trigger and ending with a useful cost cue ("Free"). Every sentence carries information, though the legal-advice disclaimer is boilerplate that slightly dilutes the core message.

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 values need not be explained, and the description covers scope, exclusions, and timing adequately for a zero-argument discovery tool. The only unaddressed item is the readOnlyHint=false annotation, which leaves a small gap in behavioral completeness.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No parameter-related information is missing or misleading.

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?

States a clear verb+resource ("Lists only the monitored GOV.UK source set") and narrows the domain to UK employment-guidance classes verified by G05. It partially differentiates from the sibling search_guidance_sources by emphasizing that it lists the source set rather than searching it, but never names that sibling outright.

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?

Gives an explicit trigger ("Use when an agent first needs to see which... classes G05 can verify") and two explicit exclusions (not legal advice, not for unrelated GOV.UK content). It stops short of naming the follow-on alternative (search_guidance_sources) by name, so the routing is implied rather than spelled out.

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