autotask_get_quote_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), which implies it's non-destructive, but doesn't mention potential errors (e.g., invalid ID), authentication needs, rate limits, or the return format. This leaves significant gaps for an agent to understand how the tool behaves in practice.

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, direct sentence with zero wasted words. It front-loads the core action ('Get a specific quote item') and efficiently specifies the key constraint ('by ID'), making it easy to parse and understand immediately.

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?

For a read tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'quote item' entails in this context, what data is returned, or how errors are handled. Given the complexity implied by sibling tools (e.g., create, update, delete operations), more context is needed for an agent to use this effectively.

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%, with the single parameter 'quoteItemId' fully documented in the schema. The description adds no additional meaning beyond implying the ID is used for retrieval, which is already clear from the schema. This meets the baseline score of 3 when the schema does the heavy lifting.

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 ('Get') and resource ('a specific quote item by ID'), making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'autotask_get_quote' or 'autotask_search_quote_items', but the specificity of 'by ID' versus broader retrieval methods is implied.

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?

No guidance is provided on when to use this tool versus alternatives like 'autotask_get_quote' (for the parent quote) or 'autotask_search_quote_items' (for multiple items). The description assumes the user already knows they need a specific item by ID, offering no context on prerequisites or typical workflows.

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