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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'No changes are made' largely restates structured data. The genuinely additive detail is the 'newest first' ordering of revisions; nothing is said about pagination behavior or the auth/scope needed to read a specific renewal term.

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?

Two short, front-loaded sentences with no filler; the ordering rule and the read-only nature come first. The closing sentence is largely redundant given readOnlyHint, so it does not fully earn its place.

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?

The output schema covers return values and annotations cover safety, so the description's main remaining obligations are usage routing and parameter meaning, and it falls short on both. An agent knows what the tool reads but not how to page through results or when it beats its siblings.

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%. The description explains none of the two parameters: it never says renewalTermId identifies which fact's history to fetch, nor that offset is a pagination cursor that pairs with the 'newest first' ordering. With no schema-level documentation to fall back on, this leaves both parameters under-specified.

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 (Read) and a precisely scoped resource (previous and new content for a saved approved renewal fact), plus an ordering rule (newest first). It implicitly distinguishes itself from mutating siblings like revise_approved_fact, but never names an alternative or explicitly contrasts with get_approved_context.

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 phrase 'saved approved renewal fact' implies this is used to inspect the revision trail of a fact after it has been approved or changed, which is a reasonable usage hint. However, there is no explicit when-to-use statement and no guidance on when to prefer get_approved_context or search_approved_terms instead.

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