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 conveys the method's two conceptual steps but says nothing about whether this is a read-only analysis, what form the result takes, latency, or whether the input is stored — none of the behavioral traits an agent needs beyond the framework idea.

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 nine-word sentence, front-loaded with the action and with no filler or repetition. It is tight, though bordering on aphoristic rather than instructive.

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 1-param analysis tool with no annotations, no output schema, and 18 mutually similar siblings, the description should say more: what the deliverable looks like and how it differs from run_pre_mortem or run_second_order_thinking. It leaves the agent under-informed for selection.

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 is a single parameter whose schema description ('Your problem, decision, project, or question to analyze with this framework') is fully documented at 100% coverage. The description adds no meaning beyond that, so the baseline of 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?

The description names a concrete method: 'Map every way this could fail, then avoid those paths' — a clear verb (map) applied to a specific object (failure modes) plus a second step (avoidance). It tells an agent roughly what the tool will do, but it does not distinguish this from the very similar run_pre_mortem sibling among the 18 run_* frameworks.

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?

No when-to-use, when-not-to-use, or alternative is given. With run_pre_mortem in the sibling list being a near-synonym for failure-mapping, the omission of any routing guidance is a real gap — the agent must guess between them from names alone.

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