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

Goes well beyond the annotations by disclosing downstream effects: Kay1 receives it by email, calls back during 7:00 AM–9:30 PM Pacific hours, and the customer gets a confirmation email if one was supplied. It also states the anti-fabrication rule and the emergency escalation path. Missing only duplicate/idempotency behavior (annotations say idempotentHint=false, but the description doesn't explain what a resend does) and what the call itself returns.

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?

Purpose is front-loaded in the first sentence, followed by outcome, then consent gating, then the emergency exclusion — a sensible order. It is dense but nearly every sentence carries operational weight; the emergency phone number and hours are long but justified safety information.

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 10-parameter, 5-required mutation with no output schema, the description covers the crucial gaps: consent, side effects, callback timing, and emergency routing. It does not tell the agent what the tool returns on success or how to handle a repeat submission, which are the remaining holes.

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 100%, so the baseline would be 3, but the description adds real meaning: the email parameter's side effect (confirmation email), the consent gating behind customer_confirmed, and the 'Do not invent details' constraint that governs the details field. Enum-driven fields (city, service, urgency, preferred_language) are left entirely to the schema, which is acceptable at full 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?

Opens with a specific verb and resource ('Send a free-estimate request to Kay1 Electric') plus the acting party ('on the customer's behalf'). This is clearly a write/send tool, distinguishable at a glance from read-only siblings like get_business_info, list_services, and list_service_areas.

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 both a positive precondition ('Only call this after showing the customer the details and getting their explicit OK') and an explicit exclusion with a redirect ('Not for emergencies... tell the customer to call (778) 900-1004'). An agent knows when to call it, when not to, and what to do instead.

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