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

Annotations only provide generic hints, but the description discloses meaningful behavior: nothing leaves without consent, up to 4 agents receive contacts under default scope, marketing partners are possible under sell_identity, deliveries/refusals are receipted, and POST /forget revokes. This goes well beyond the structured fields and gives the agent important side-effect awareness.

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 every sentence adds value: purpose, prerequisites, scope behavior, consent boundary, and lifecycle/revocation. It is front-loaded with the core action and does not repeat schema field names mechanically.

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 9-parameter tool with nested consent and no output schema, the description covers the most important operational context: prerequisites, consent, scope, receipts, and revocation. It does not elaborate on optional contact fields or the exact response shape, but the supplied context is sufficient for safe invocation in most agent flows.

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 must compensate. It explains quote_id, name, phone, and consent, but leaves parameters like best_time, email_address, and preferred_channel without additional meaning in the description or schema. The consent object is clarified well, but several parameters remain undocumented.

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 who can quote firm and bind." It clearly separates this tool from siblings by anchoring it to quotable/bindable agent contact and explicitly requiring consent. The title reinforces the consent requirement without relying on it.

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 names the required prerequisite (quote_id from get_quotes), the required consumer approvals, and how consent can be obtained. It explains the two scope variants and their different sharing targets, but does not explicitly name sibling tools to exclude or state when not to use this tool.

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