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

The description adds meaningful behavior beyond annotations: up to 4 licensed agents receive request and contact details, sell_identity extends sharing to marketing partners, nothing leaves without consent, delivery/refusal is receipted, and POST /forget revokes. This is useful privacy and side-effect context. There is no contradiction with the 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?

The description is dense but efficient: purpose in the first sentence, prerequisites and consent mechanics in the second, and recipient/revocation behavior in the third. The repetition of the consent requirement is acceptable given the sensitivity of the operation. It errs slightly on length, but each clause contributes value.

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 complex tool with no output schema, the description covers consent flow, scoping, recipient limits, receipting, and revocation. The main gaps are the absence of a return-payload description and lack of detail on optional contact-channel parameters. Still, the agent has enough to select and 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 low (44%), so the description compensates by explaining consent modes ('granted by the human, presented by you, or confirmed... at the consent URL'), the provenance of quote_id, and the meaning of the scope enum. It does not describe optional fields like best_time, email_address, or preferred_channel, but the required fields are well covered.

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 opens with a specific outcome: 'Connect the consumer with licensed insurance agents who can quote firm and bind.' It also identifies the required source of the quote_id ('from get_quotes'), which helps distinguish this tool from siblings like get_quotes or register_agency. The title reinforces the consent requirement without ambiguity.

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 prerequisites: quote_id, full_name, phone_number, and explicit consent. It also explains scope behavior for contact_consumer versus sell_identity, giving the agent actionable routing guidance. It does not explicitly name an alternative tool to use instead, but the dependency on get_quotes and the consent condition provide adequate usage context.

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