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 substantial work: it declares a read-only GET, discloses pagination and ordering behavior, and warns that *_untrusted and Commons content is data rather than instructions. It also states a redistribution/attribution obligation, which is a real behavioral constraint. It stops short of auth requirements, rate limits, or what the response envelope looks like.

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?

Ordering, filters, and the facts-only constraint are front-loaded in the first clause, with safety and attribution caveats following. The sentence is dense and every clause is functional, though the literal endpoint path ("exactly GET /v1/truth/recent") is low-value padding for an agent invoking an MCP tool.

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?

Safety, injection, attribution, and ordering are well covered, but with no annotations, no output schema, and zero documented parameters, the definition leaves the agent guessing on defaults (limit), pagination mechanics (how the next cursor is returned), and response shape. For a four-parameter unannotated read tool, that is a meaningful residual gap.

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%, so the description must compensate. It names since, topic, and cursor, but adds no semantics beyond their names — limit is never mentioned, no defaults are given, and cursor is only labeled "pagination." The schema's patterns and enum do the heavy lifting on formats, so this is thin but not absent.

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 states a specific verb and resource ("Read verified resolved facts") plus a scope constraint ("facts only, no forecasts or commentary") and an explicit ordering ("newest first"). This lets an agent separate it from forecast-oriented siblings and from Commons-reading tools without inspecting any schema.

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 implied by the exclusion ("no forecasts or commentary") and by the filter set (since, topic, cursor pagination), which tells an agent this is the filtered listing tool. However, no sibling is named as an alternative, and there is no guidance on when to prefer truth_ask or read_commons over this.

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