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

No annotations are provided, so the description carries the full disclosure burden. It usefully establishes that the data is the caller's own prior translations and that the operation is a non-mutating listing, but says nothing about ordering, recency, pagination behavior, or the shape of a returned entry.

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 front-loaded sentence that names the action, the resource, and the motivation with zero filler. Nothing is repeated and nothing needs trimming.

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 simple two-parameter read tool with 100% schema coverage this is close to adequate, but with no annotations and no output schema the description leaves the return value ('previous translations') undefined, so an agent cannot tell what it will actually get back or how to reuse it.

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?

Both parameters (limit, offset) are fully documented in the schema, including defaults and bounds, so the schema does the heavy lifting. The description adds no parameter-level detail such as ordering semantics or whether offset paging is stable, so the baseline 3 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?

States a specific verb ('Lists') and resource ('the user's previous translations'), making the operation immediately clear. It does not differentiate itself from any sibling, but no sibling in the list (translate_text, refine_translation, etc.) overlaps with a history/listing operation, so confusion risk is low.

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 clause 'so prior work can be reused instead of regenerated' implies why an agent would call it (look up an existing translation before re-translating), but it never states when to use this versus re-running translate_text or refine_translation, and gives no exclusions or prerequisites.

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