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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so "Nothing is created" is largely redundant. The description does add value by disclosing the response content — the amount charged, what is included, and delivery terms — since there is no output schema. It stops short of quoting validity, expiry, or currency details.

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 tight sentences: the first front-loads what is priced and from which inputs, the second covers output and the no-side-effect guarantee. No filler.

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 simple read-only quoting tool with full schema coverage and annotations that already declare safety, the description covers inputs, output content, and side-effect status. Remaining gaps (price validity, whether the quote locks in a rate) are minor.

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%, so the schema already explains qty ranges, location format, and the min_reviews cost trade-off. The description only restates the parameter list (business types, locations, quantity, optional review bar) without adding syntax or semantics beyond the schema, so the 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?

States a specific verb and resource ("Exact price for a lead list") plus the inputs that drive the quote, which separates it from the generic get_pricing sibling and from create_order. An agent can tell what it produces without opening the schema.

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?

"Nothing is created" implicitly positions this as the pre-purchase step before create_order, but no alternative is named and no explicit when-to-use/when-not guidance is given (e.g. quote vs. sample leads vs. pricing). Usage must be inferred from the tool name and siblings.

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