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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are ordered reverse-chronologically and items are intentionally lightweight (not full job payloads), which sets agent expectations about result shape. It does not mention how deep history goes or how pagination behaves, so it is not exhaustive.

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 sentences, zero filler. The core purpose and ordering come first, and the disambiguation against the sibling follows, so the most decision-relevant information is front-loaded.

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 two-parameter, fully annotated, read-only list tool with complete schema coverage, this is close to sufficient: purpose, ordering, result weight, and the sibling alternative are all present. The only remaining gap is depth of history or pagination behavior, which an agent might want when the list is large.

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 100% for both parameters (page, size with defaults and bounds), so the schema does the parameter work. The description contributes only the ordering context, not any meaning about page/size semantics, which is the expected baseline-3 outcome when the schema is already complete.

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 and resource ("List window replay job history") plus the ordering guarantee (reverse-chronological), which an agent could not infer from the name alone. It also names a sibling, lexq_replay_status, so the tool is distinguishable within the replay tool family (start/status/cancel/export/decision/list).

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?

Explicitly routes the agent: use this for lightweight list items, use lexq_replay_status for summary and changed samples. That is a clear when-to-use-this-vs-that statement. It stops short of a full 5 because other plausible alternatives (lexq_replay_export for full payloads, or pagination guidance for large histories) are not addressed.

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