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

No annotations are supplied, so the description carries the full burden. It does disclose the two returned fields (fact ids and verification states), which is genuine behavioral value, but says nothing about result size, ordering, pagination, or whether the list covers all facts in the domain.

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 front-loaded sentence with no filler, stating the operation before the domain qualifier. The trailing '(debtuk)' restates the tool-name prefix and is mildly redundant, but it costs almost nothing.

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 zero-parameter read tool with no output schema, the description does specify the return fields, which is the main thing an agent needs. Remaining gaps are the relationship to debtuk_get_fact and any notion of list size or exhaustiveness.

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 there is no parameter semantics for the description to explain; the baseline of 4 applies. The description does not mislead by implying filtering options that do not exist.

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 gives a specific verb (List) and resource (fact ids + verification states) scoped to the debtuk domain. It is visibly distinct from sibling debtuk_get_fact (single fact retrieval) and debtuk_changes (change history), though it never names those alternatives.

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: 'List' suggests enumeration to discover ids, presumably before calling debtuk_get_fact, but the description never states that workflow, nor when to prefer debtuk_changes. An agent must infer the sequencing from the sibling naming pattern.

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