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

Annotations declare readOnlyHint=true and destructiveHint=false, so the description is consistent with a read-only analysis. The description adds minimal behavioral context—it does not mention any side effects, performance, or required preconditions beyond the parameters. With annotations covering the safety profile, the description meets the baseline but does not enrich the behavior beyond what the annotations already provide.

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, concise sentence that front-loads the core purpose ('Benchmark the business front door') followed by the inputs and expected output. There is no fluff, and every phrase contributes to understanding the tool's function. The structure is highly efficient.

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?

The description fully explains what the tool does and what inputs it takes, and an output schema exists, so the return format is handled structurally. However, it lacks any guidance on when to choose this tool among the numerous sibling diagnostics. Given the high sibling count and the simple read-only nature, this is a notable gap for an agent deciding which tool to invoke.

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 description coverage is 100% for all four parameters, including clear definitions and enum values for frontDoorProfile. The tool description does not add any additional semantics or context about how the parameters are used beyond what the schema already provides. Since the schema fully documents the parameters, a baseline of 3 is appropriate; the description adds no extra value here.

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 purpose: benchmarking the business front door using lead volume, customer value, and intake profile to estimate monthly and annual revenue at risk. The verb 'benchmark' and resource 'business front door' are specific, and the inputs and output are explicitly listed. While it doesn't name a specific sibling to contrast with, the unique focus on front door and revenue at risk differentiates it from other diagnostic tools.

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 no guidance on when to use this tool versus the many similar siblings (e.g., run_revenue_leak_diagnostic, run_competitor_intake_scanner). It does not state conditions for selection, alternatives, or exclusions. The agent is left to infer its applicability from the name alone, which is insufficient given the cluster of closely related tools.

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