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

Annotations only provide readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds substantial behavior beyond this: consent provenance, scope-based sharing limits (up to 4 licensed agents vs marketing partners), the guarantee that nothing leaves without consent, receipting of deliveries/refusals, and POST /forget revocation. This is exactly the contextual disclosure an agent needs.

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 about five sentences, front-loads the core purpose, and every sentence adds operational value: prerequisites, consent, scope, privacy guarantee, and revocation. There is no filler or repetition.

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, no-output-schema tool, the description covers prerequisites, consent mechanics, scope limits, and revocation well. The only meaningful gap is that it does not state what a successful response contains or what the agent should expect back after invoking the 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 description coverage is only 44%, so the description must compensate. It does explain quote_id, full_name, phone_number, and the consent object including scope semantics and the consent URL. However, it leaves best_time, email_address, preferred_channel, verify_token, street_address, and evidence to the schema, so compensation is partial.

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 verb and resource: 'Connect the consumer with licensed insurance agents who can quote firm and bind.' It clearly names the needed inputs and even references get_quotes as the source of quote_id, which distinguishes it from sibling tools like check_eligibility or agency_status.

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 gives clear prerequisites: quote_id from get_quotes, consumer name and phone, and explicit consent. It implies this tool is used after get_quotes and before agent contact. It does not explicitly list when not to use it or compare against sibling alternatives, so it stops short of a 5.

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