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

Annotations already declare the write/open-world/destructive/non-idempotent profile, so the bar is lower. The description adds real context beyond that: it emails the user the businesses' replies, and on missing details it returns which fields are absent with a directive to ask the user rather than invent. It stops short of explaining the irreversible/destructive nature flagged by 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?

Four tight sentences, front-loaded with the use condition, then behavior, then validation handling, then the exclusion. No filler; every sentence changes how an agent would call it.

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?

No output schema exists, yet the description covers the trigger, side effect (emails replies), missing-field handling, and negative scope. Only the semantics of a few secondary parameters are left thin, which is minor for a well-scoped workflow 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 only 29%, so the description carries more burden. It clarifies the 1-3 business limit (mapping to vendor_slugs bounds) and that details are the fields the businesses asked for, but says nothing about service, notes, or the customer_* fields. Partial compensation for a low-coverage schema.

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 (send an approved structured quote request to 1-3 Servana businesses) and ties it to the originating sibling, the prepare_quote_request form. It also explicitly carves out what it is not (no booking, no payment), so an agent can distinguish it from siblings without opening a 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?

Gives an explicit trigger (user approved a structured quote request, usually from prepare_quote_request) and explicit exclusions ("Do not use to book or pay"). The alternative source of requests is named, leaving nothing to inference.

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