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

With no annotations supplied, the description carries the full burden and does disclose a genuinely useful behavioral trait: the tool refuses with a do_not_answer outcome when a fact is drifted or unverified and never guesses. That tells an agent to handle a non-answer case. It stops short of explaining what 'drifted' means, what the success payload looks like, or any auth/rate constraints.

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 short sentences, front-loaded with the purpose and followed by the failure semantics. No filler and nothing that fails to earn 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?

For a simple one-parameter read tool with no output schema, the description covers purpose and refusal behavior adequately. It leaves the agent guessing about fact_id provenance and the shape of a successful result, which matters since there is no output schema to fall back on.

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 description coverage is 0% for the single fact_id string, and the description adds nothing about its format or where a valid ID comes from (presumably privacyuk_list_facts). With one undocumented parameter, the description fails to compensate for the coverage gap.

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 specific verb and resource ('Get one verified fact') scoped to the privacyuk pack, which is how it is distinguished from the many sibling *_get_fact tools. The scope is clear, though the differentiation rests entirely on the pack name prefix rather than any explicit contrast with siblings.

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?

Usage is only implied: fetch a single fact when you already have its identity. There is no explicit guidance on when to reach for this versus privacyuk_list_facts or privacyuk_changes, and no prerequisites or exclusions are stated.

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