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

With no annotations, the description carries the full disclosure burden and does well: it reveals that reporting feeds a shared crowd view, acts as safety telemetry, is token-scoped, and is free. It does not cover idempotency or repeated-report effects, but the main side effects and scope are clearly stated.

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 dense but well-organized: purpose, parameter list, dual purpose, and scope/cost are each covered efficiently. The em-dash asides earn their place, though the text is longer than strictly necessary.

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 6-parameter tool with no output schema and no annotations, the description covers the caller context, the parameters, the side effects, and the cost/scope. The main gap is the lack of semantics for three parameters裡class, family, confidence, which keeps it from being fully complete.

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%, and the description lists all six parameters but only clarifies 'succeeded' ('did the retry work?'). The undocumented parameters failure_class, family, and confidence are named but not given meaning, so the description only partially compensates for the schema gap.

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 states a specific verb and resource: report the outcome of an auto-applied fix alert. It goes further to explain the caller (self-heal interceptor) and distinguishes this from a generic outcome report by tying it to telemetry and the shared crowd view used by what_others_did.

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 gives clear context: use this after a gate-applied fix and its retry, and it explains why reporting matters. It does not explicitly spell out when not to use it or name alternatives, but the self-heal interceptor framing strongly implies the intended invocation path.

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