autotask_create_quote_item

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

No annotations are provided, so the description carries full burden. It discloses default values for discounts and isOptional, and the mutual exclusivity of item references. However, it doesn't mention side effects (e.g., whether it recalculates quote totals) or permissions needed, leaving some behavioral gaps.

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 extremely concise, using only three sentences to cover purpose, key rule, required fields, and defaults. It front-loads the core action and critical constraint, with no wasted words.

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 (15 parameters, no output schema), the description provides sufficient guidance for a create operation. It omits return value details (which might be expected from a create tool) and potential error conditions, but the constraints and defaults are well-covered. The schema's rich descriptions partially compensate for the lack of output schema.

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?

The input schema has 100% description coverage for all 15 parameters. The description adds value by summarizing the key rules (set exactly one item reference, required fields, defaults) and explaining the quoteItemType auto-determination, 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 the verb 'Create' and the resource 'line item on a quote', distinguishing it from siblings like autotask_create_quote (creates the quote itself) and autotask_update_quote_item (updates an existing item). The tool is uniquely for adding items to quotes.

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 specifies to set exactly one item reference (serviceID, productID, or serviceBundleID) and lists required fields (quoteId, quantity) and defaults. It does not explicitly mention when not to use this tool versus alternatives like autotask_update_quote_item, but the context of creation vs. update is implied.

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