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

With no annotations provided, the description carries the full burden of transparency. It discloses that the tool is free and read-only (audit), and lists the outputs: a risk score, missing safeguards, revenue-at-risk estimate, integration kit, and checkout path. This is detailed, but lacks mention of any side effects or authorization requirements.

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 a single sentence that front-loads the main action and then lists key outputs. Every word adds value, with no redundancy or filler. It is appropriately scoped for a simple audit tool.

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 complexity of 8 parameters (2 required), no output schema, and no annotations, the description should at least touch on the inputs. It does not explain what arguments are needed or their roles, leaving a significant gap in the agent's understanding of how to invoke the tool correctly.

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?

The input schema has 8 parameters with 0% description coverage, and the tool description does not explain any of them. The description focuses entirely on outputs, providing no meaning or constraint for inputs like 'stack', 'idempotency', or 'retry_policy'. The agent would have to infer parameter purpose from names alone.

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 performs a free reliability audit of a lead-delivery workflow, using a specific verb ('Run') and resource ('audit of a lead-delivery workflow'). The title 'Audit Lead Workflow' aligns, and it is distinct from sibling tools which focus on comparison, evaluation, or checkout.

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 implies usage for auditing reliability and obtaining a risk score, but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. There is no guidance on when not to use it.

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