autotask_create_quote_item

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Create' without mentioning side effects, authorization requirements, error conditions, or what happens if constraints are violated (e.g., multiple item references). Lacks transparency for a write operation.

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?

Three sentences, each with a clear purpose: purpose, constraint, required/defaults. No unnecessary words. Highly efficient and easy to parse.

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?

Covers main action, constraint, and defaults but omits output/return value, preconditions (e.g., quote must exist), and error handling. Given no output schema, description should fill these gaps. Could be more 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 description coverage is 100%, so baseline is 3. The description adds minimal extra value by summarizing the mutual exclusivity constraint and defaults, but the schema already describes each parameter adequately. No significant enhancement.

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' with specific verb and resource. It distinguishes from siblings (e.g., create_quote, update_quote_item) by focusing on adding an item and includes the critical constraint of setting exactly one item reference.

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 guidelines: set exactly one item reference, required fields (quoteId, quantity), and defaults. It helps the agent know when to use this tool but does not explicitly mention when not to use it or alternative tools for updating/deleting.

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