autotask_search_quote_items

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

The description indicates a read-only search operation but does not disclose additional behavioral traits such as permissions, rate limits, or response size, relying solely on the schema for pagination hints.

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, front-loaded sentence with no extraneous words, efficiently conveying the tool's purpose and typical use.

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?

Without an output schema, the description lacks detail on return values, search behavior (e.g., exact vs fuzzy matching), and does not explain the relationship to quotes or quote items, leaving gaps for agent understanding.

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 the description adds minimal value beyond restating the primary filter (quote ID). No new semantic information is provided.

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 'Search for quote items' using a specific verb and resource, and distinguishes from sibling tools like autotask_search_quotes and autotask_get_quote_item by focusing on items.

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 implies usage by recommending filtering by quote ID but does not explicitly state when to use this tool over alternatives like autotask_search_quotes or autotask_get_quote_item.

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