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

With no annotations, the description carries the full disclosure burden. It says the tool returns a changelog, but not the recency window (how far back "recent" goes), ordering, result limit, whether it is read-only, or whether it requires any auth — all things an agent needs before deciding to call it.

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 short phrase with no filler, and the resource is front-loaded. It is efficient, though the brevity edges toward under-specification rather than precision.

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, no-output-schema tool the bar is low, and the description does convey the broad shape of the response. Still, "recent" is undefined and the nature of a "verification change" record is left ambiguous, leaving the agent unable to predict what comes back.

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 does not needlessly imply hidden inputs.

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?

"Recent verification changelog" names a resource (a changelog of verification events) scoped to marriageuk, which is more than a tautology. However, it never says what a "verification change" actually is or how this differs from the sibling marriageuk_get_fact / marriageuk_list_facts tools, so the agent must guess at the payload.

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 versus the other marriageuk tools, no prerequisites, and no exclusions. The only implicit guidance is the word "recent," which hints at a freshness-check use case but is never made explicit.

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