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

Annotations already mark it as read-only; the description adds meaningful extras: cost ($0.08), API key requirement, and the cross-referencing behavior against failure patterns and success templates. No contradictions with annotations.

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?

Two sentences with a clear action→process→outcome flow. Includes cost and auth without verbosity; every part earns its place.

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?

Given the 2 params, full schema coverage, and no output schema, the description sufficiently explains purpose, input, process, output, cost, and prerequisites. It could detail the recovery plan format but is adequate for a self-audit tool.

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 descriptions and an example for execution_trace, plus context description. The tool description does not add parameter-level detail, so baseline 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 clearly states a specific action (submit an agent execution trace) and a concrete outcome (returns a risk-flagged recovery plan via Hive cross-referencing). It distinguishes itself from siblings by focusing on auditing agent behavior against 26,000+ patterns.

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?

It implies use when you want to catch silent brittle behavior before losses, which gives clear context. It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to select this tool over generic hive or agent tools.

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