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

Annotations already mark the tool read-only and idempotent, and the description adds useful output-context guarantees: the article is returned with its evidence clock and passing quality receipt, and the content is not rewritten. This is consistent with readOnlyHint=true.

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 sentence that front-loads the action and resource, with every clause adding meaningful detail: 'canonical', 'evidence clock', 'passing quality receipt', and 'no rewritten facts'. There is no filler or repetition of schema content.

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, this is complete: it identifies the target article, what is included in the result, and the integrity guarantee. Although there is no output schema, the description gives enough to know what a successful call returns.

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?

There are no parameters, so the input schema is trivially complete and the description does not need to document arguments. The baseline of 4 applies.

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?

Clearly names the operation 'Read' and the resource ('canonical full-text Undertow editorial'), with qualifiers like 'evidence clock' and 'passing quality receipt' that explain what the output contains. It is unambiguous and easily distinguishable from the unrelated sibling tools.

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?

The description signals use for retrieving the authoritative Undertow editorial, and the 'no rewritten facts' phrase indicates this is the original rather than a summary or rework. It does not name explicit alternatives or exclusion cases, but the zero-parameter schema and unique resource make the intended use clear.

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