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

No annotations are provided, so the description carries the full burden. It does disclose the return payload shape (ids plus verification states), which implies a read-only enumeration, but it says nothing about ordering, pagination, volume of results, or whether 'verification states' has a fixed vocabulary.

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 sentence, front-loaded with the verb and the most decision-relevant detail (that it returns ids, not fact content). Zero filler and nothing to trim.

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?

With no output schema, the description must explain the return value and does so only at a high level: it names the fields but not what a verification state looks like or how many results come back. For a simple enumerator this is close to sufficient, but the 'verification states' term is left undefined and the handoff to get_fact is unstated.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly signals that the call is unfiltered and unconditional.

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 ('List') and specific resources ('fact ids + verification states'), and the '(broadbanduk)' marker scopes it to the broadband domain, which is what separates it from the ~20 other *_list_facts siblings. It does not explicitly distinguish itself from broadbanduk_get_fact or broadbanduk_changes, but the list-vs-get-vs-changes pattern is legible.

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?

No when-to-use guidance and no alternatives named; the agent must infer that this is the entry point for discovering ids to feed into broadbanduk_get_fact. Nothing states when to prefer this over broadbanduk_changes, which presumably surfaces the same ids with change information.

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