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

The description discloses behavioral traits beyond annotations: it creates/updates jobs, syncs to accounting, generates payment links, and sends notifications. Annotations show destructiveHint=false and readOnlyHint=false, consistent with mutation without destruction. No contradictions.

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 a single paragraph of three sentences, front-loading the main purpose and listing actions efficiently. Every sentence adds value; no filler.

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 complexity of a multi-step pipeline, the description summarizes the end-to-end process well. Output schema exists, so return values are covered. Lacks details on prerequisites (e.g., quote must be in 'accepted' status) and error conditions, but overall sufficient for an agent to understand scope.

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 baseline is 3. The description only mentions the parameters by name in context ('quoteId,' 'discount,' 'customDueDate') without adding semantics beyond the schema. No added value.

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's purpose: converting an accepted quote into a full invoice pipeline. It enumerates specific steps (create/update job, sync to accounting, generate payment link, notify customer, alert team), which distinguishes it from sibling tools like invoicing.generate or workflows.trigger_invoice that perform subparts of this workflow.

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 implies the quote must be accepted ('Convert an accepted quote') and that the tool handles the full 'quote-accepted → paid lifecycle.' It does not explicitly state when not to use alternatives, but the sibling tools provide context. Without explicit exclusions, it loses one point.

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