autotask_create_quote_item

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action (create) and defaults, but lacks information on side effects, authorization requirements, error conditions, or what happens if constraints are violated (e.g., setting multiple item references). The agent might need to infer these from context.

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: two sentences with no wasted words. It front-loads the purpose and follows with essential rules and defaults. Every sentence adds value.

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 high schema coverage and no output schema, the description covers the key aspects: purpose, constraints, required params, and defaults. It does not explain the return value or behavior on error, but for a creation tool this is acceptable. Slightly more detail on expected outcome would push it to 5.

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%, but the description adds critical meaning beyond the schema by stating the mutual exclusivity of serviceID, productID, and serviceBundleID, and listing default values for optional parameters. This significantly aids correct invocation.

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'. It differentiates itself from sibling create tools (e.g., autotask_create_quote) by specifying it adds items to an existing quote. The phrase 'Set exactly ONE item reference' adds specificity.

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 provides a clear rule: set exactly one of serviceID, productID, or serviceBundleID. It also lists required parameters (quoteId, quantity) and defaults. However, it does not explicitly mention when not to use this tool (e.g., for updating use update_quote_item) or alternatives, which would be helpful.

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