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

The description goes well beyond the annotations by disclosing real-world side effects: up to four licensed agents receive the request and contact details, sell_identity permits sharing with marketing partners, nothing leaves without consent, deliveries and refusals are receipted, and POST /forget revokes consent. This is rich behavioral context that annotations alone do not 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 four dense, information-packed sentences with no filler. It front-loads the core purpose and required inputs, then adds consent mechanics, scope behavior, and revocation in a logical order. Every sentence 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?

For a tool with a nested consent object, scope options, and consent-revocation behavior, the description covers the essential operational context well: prerequisites, consent flow, scope differences, and side effects. It lacks an explicit statement of return values or outputs, but with no output schema provided, the description is still strong enough for an agent 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?

Schema description coverage is only 44%, so the description carries a heavier burden. It does add important semantics for the required parameters: quote_id comes from get_quotes, full_name and phone_number identify the consumer, and consent can be granted/presented/confirmed in specific ways. However, optional parameters like preferred_channel, best_time, and email_address still lack meaningful description coverage.

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 uses a specific verb and resource ('Connect the consumer with licensed insurance agents') and clearly states the consent requirement and the purpose ('quote firm and bind'). It also references get_quotes, which distinguishes it from sibling tools without needing to open their schemas.

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 clearly states the key prerequisite (quote_id from get_quotes), the required consumer details, and the consent precondition. It also explains scope-based behavior (contact_consumer vs sell_identity). It does not explicitly enumerate when-not-to-use alternatives, but the context is sufficiently clear.

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