autotask_search_quote_items

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

No annotations are provided, so the description bears full burden. It does not disclose pagination behavior (though pageSize is in schema), whether results are returned in any order, or if there are any constraints on the searchTerm. The description is minimal on behavioral aspects.

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 concise sentence. It is front-loaded with main purpose and common filter. Could be slightly more informative without being lengthy.

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, 100% schema coverage, and no output schema, the description is adequate but lacks detail on return format or behavior beyond filtering. It's complete enough for basic use but not for advanced scenarios.

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?

The description mentions filtering by quote ID, which adds context beyond the schema description for that parameter. However, schema coverage is 100% so the bar is higher; the description does not add much extra meaning beyond what the schema already provides.

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 says 'Search for quote items, typically filtered by quote ID', which clearly indicates the tool searches for quote items with a common filter by quote ID. It differentiates from sibling tools that are create or get operations for specific entities.

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 the primary use case (filter by quote ID) but does not explicitly state when to use this tool over other search tools like autotask_search_quotes or autotask_search_products. No alternatives or when-not-to-use guidance is provided.

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