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

Annotations declare readOnlyHint=false with destructiveHint=false, so an agent knows this writes state benignly. The description adds nothing about that write: it does not say whether the report is final, whether it closes the session, or whether an outcome can be corrected after submission. With annotations present the bar is lower, but this adds essentially no behavioral context.

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, so it is appropriately sized. Its problem is sparseness rather than bloat, which is scored under other dimensions.

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 four-parameter write tool with 50% schema coverage, no output schema, and an ambiguous pointer ('the answer'), the description is too thin. It omits how to choose an outcome value, what the report affects, and how it relates to sibling recovery tools.

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 50%: api_key and request_id are documented in the schema but outcome and session_id are not. The description only partly compensates by tying session_id to a prior answer, and it gives no guidance for selecting among the five outcome enum values, which is the core semantic decision of this tool.

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 pairs a specific verb ('report') with a specific resource ('whether a recovery plan worked'), so the action is clear. It does not differentiate itself from siblings like assess_escalation or recommend_recovery, which also concern recovery outcomes.

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?

'using the session_id from the answer' implies this is called after another tool returns an answer, giving an implicit sequencing cue. However, 'the answer' is never identified as recommend_recovery, assess_escalation, or another sibling, and there is no when-not guidance.

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