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

Annotations already indicate destructiveHint and readOnlyHint false. The description adds meaningful behavioral context: the trade stops counting, but the row is kept because there is no hard delete by design. This clarifies the actual destructive scope beyond the annotation flags, though it does not address irreversibility or permissions.

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?

The description is two sentences, front-loaded with the core purpose and use cases, then adds essential nuance about row retention. Every clause adds value, and it is concise without sacrificing clarity.

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 destructive tool with no output schema and two well-documented parameters, the description is complete enough: it explains what happens to the trade's stats, the use cases, and the no-hard-delete design. It does not describe return values, but that is not essential for this operation and no output schema exists.

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 coverage is 100%, with both parameters (trade_id and confirm) already documented in the input schema. The description does not add new parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 clearly states the tool's function: removing a trade from Trading Journal stats so it stops counting toward win rate, P&L, and emotion breakdown. It uses a specific verb with a clear resource and distinguishes the semantic from related tools like close_trade or update_trade by emphasizing statistical exclusion while keeping the row.

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 description provides clear use cases: mis-entry, duplicate, or practice trade logged by mistake. It implies when this tool is appropriate but does not explicitly mention when not to use it or contrast it with alternatives like close_trade or update_trade, so it falls just short of a 5.

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