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

No annotations are supplied, so the description carries the full burden and largely drops it. It does not say what a changelog entry contains, how far back 'recent' reaches, how entries are ordered, or whether the result can be empty — all things an agent needs before deciding to call a zero-parameter tool whose output is unspecified.

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?

The description is a single fragment with no wasted words, but it is terse to the point of under-specification rather than genuinely efficient. There is no front-loaded verb or scope statement to anchor the reader.

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 no-parameter tool with no annotations and no output schema, the description is the only channel available to explain the returned data, and it does not. An agent must call it blind to learn what a changelog record looks like.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not falsely suggest any inputs 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 phrase 'Recent verification changelog (passportuk)' identifies a resource (a changelog) and a recency scope, and the parenthetical domain tag separates it from the many sibling *_changes tools. However, it uses no verb and leaves 'verification' ambiguous — an agent cannot tell whether this is a log of verification results, verification rule changes, or fact-check status changes.

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?

There is no statement of when to call this rather than passportuk_get_fact or passportuk_list_facts, and no condition such as 'use to check whether a previously returned fact has been revised'. The only implied usage comes from the word 'changelog' itself, which is inference, not guidance.

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