autotask_search_quote_items

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Search for quote items', which is a read operation. It does not mention pagination behavior (though pageSize parameter exists), rate limits, or that all parameters are optional. The schema covers parameter descriptions, but the description adds no behavioral context beyond that.

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, clear sentence. It is concise and front-loaded with the key action. No unnecessary 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 tool has 3 parameters, no output schema, and no annotations, the description is minimal. It omits that all parameters are optional and does not summarize default page size or search behavior. The schema fills some gaps, but for a search tool, the description could be more informative about typical usage and results.

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 little new meaning. It reinforces that quoteId is a typical filter, but the schema already says 'Filter by quote ID (recommended)'. No additional semantics for searchTerm or pageSize. Baseline 3 is appropriate.

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 tool searches for quote items, with a typical filter by quote ID. It distinguishes from siblings like autotask_get_quote_item (retrieve single) and autotask_search_quotes (search quotes, not items). However, it could be more specific about what 'quote items' are, but in context it is adequate.

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 mentions 'typically filtered by quote ID', implying a common use case. However, it does not explicitly state when to use this tool versus alternatives (e.g., get_quote_item for a single item, search_quotes for quotes). No when-not-to-use guidance is given.

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