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

The description lists all pipeline steps, disclosing side effects (job creation, SMS, calendar sync, notifications). Annotations declare readOnlyHint=false and destructiveHint=false, which are consistent. However, it does not discuss failure handling or reversibility, which would add transparency.

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?

Two sentences: the first is a bullet list of steps, the second is a concise tagline. No wasted words, information is front-loaded.

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's complexity (multi-step pipeline with multiple parameters) and the presence of an output schema, the description covers the overall process and key steps. It lacks mention of prerequisites (e.g., lead must exist) but is generally complete.

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% with clear descriptions for each parameter (leadId, autoQuote, notifyTeam, autoSchedule, notifyCustomer). The description ties them to the pipeline flow (e.g., autoQuote → auto-quote step), adding value beyond the raw schema.

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 it processes a new lead through a full pipeline (AI analysis, auto-quote, job creation, calendar sync, notifications), distinguishing it from sibling workflow tools like workflows.quote_to_invoice or workflows.schedule_job which handle only part of the process.

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 says to use this for 'Full pipeline processing for a new lead,' but does not explicitly mention when to avoid it or alternatives like individual workflow steps. However, the context signals from sibling names give implicit guidance.

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