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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only the analytical method ('empirical argument verification'), and says nothing about output shape, runtime, or how the horizon is used — adequate but thin given the annotations do the heavy lifting.

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 with no filler or repetition. It is dense with jargon ('empirical argument verification') but every clause carries information about what the tool produces.

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?

With no output schema, the description is the only place return expectations could be set, and it only gestures at results ('failure modes and early warning indicators') without describing format or scope. Two parameters and an existing annotation set keep the burden modest, so this is minimally viable rather than inadequate.

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%, so both 'premise' and 'horizonMonths' are already documented with meaning, defaults, and limits. The description contributes no additional parameter semantics, which is the expected baseline when the schema is 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?

The description names a specific verb and artifact — 'executes an adversarial pre-mortem' — and enumerates the deliverable (failure modes, early warning indicators). It is clearly distinct from data-flavored siblings like ecca_nutrition or ecca_money, though it doesn't explicitly contrast with the closer analytical siblings ecca_verify or ecca_decision_tournament.

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?

There is no statement of when to choose this tool over ecca_verify, ecca_decision_tournament, or ecca_research, all of which are plausibly adjacent analytical tools. The agent must infer the use case from the phrase 'strategic plan, architecture, or business premise to stress-test' in the schema, not from the description.

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