autotask_create_quote_item

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

No annotations provided, so description carries full burden. It discloses that exactly one item reference must be set and defaults for discount fields, but does not describe side effects (e.g., recalculation) or error conditions. Adequate but not exhaustive.

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 concise sentences covering action, constraints, and defaults with no redundant words. Front-loaded with the primary action.

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?

Sufficient for an experienced user: key constraints and required fields are stated. Could mention expected return or error handling, but given 15 parameters and no output schema, it covers the essentials.

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 parameters are described in schema. The description adds value by emphasizing the mutual exclusivity constraint and listing defaults, which goes beyond the schema's individual descriptions.

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 'Create a line item on a quote' and specifies the verb and resource. It distinguishes from siblings like autotask_create_quote (creates quote) and autotask_delete_quote_item by focusing on adding a line item.

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?

Provides explicit constraints: 'Set exactly ONE item reference' and lists required fields and defaults. Does not explicitly mention when to use alternatives like search_quote_items or update_quote_item, but clearly indicates how to use this tool.

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