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

Annotations already indicate readOnlyHint=false, so the tool modifies data. The description adds that it can 'auto-generate draft quotes', which is a key behavioral trait. However, it does not elaborate on side effects (e.g., creation of quotes, potential duplicates) or other behaviors beyond what annotations convey.

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 three sentences with no unnecessary words. It front-loads the purpose, then details functionality, then adds a requirement. Every sentence adds value and there is no fluff.

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?

Given the tool has 3 parameters and an output schema, the description covers the core functionality (suggesting upsells, auto-quoting) and the requirement. It does not explain return values, but the presence of an output schema handles that. It is mostly complete for an agent to understand what the tool does.

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 100%, and the schema already explains parameters (jobId, leadId, autoQuote) well. The description mentions analyzing job history and auto-generating quotes, which aligns with the schema, but does not add new meaning beyond what the schema provides.

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 clearly states the tool is an 'AI-powered upsell/cross-sell engine' that analyzes job history against a service catalog to suggest services and can auto-generate quotes. This is a specific verb and resource, and it distinguishes from siblings like 'quotes.ai_price_suggestion' which focuses on pricing, not suggestions.

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 mentions 'Requires Pro plan' as a prerequisite, but gives no guidance on when to use this tool versus alternatives, nor when not to use it. Sibling tools like 'quotes.create' or 'workflows.follow_up_quote' are related but not discussed.

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