autotask_search_quotes

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

Description lacks behavioral details such as pagination (pageSize parameter hints but not stated), return format (list vs single), rate limits, or auth requirements. With no annotations, the description should provide more context about the operation's behavior and response, but it only says 'search with filters'.

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?

Very concise (4 words), but at the expense of completeness. It does not waste words, but given the complexity of the tool (5 parameters, no output schema), it is under-specified. A balance between conciseness and informativeness is needed.

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 search tool with 5 optional parameters and no output schema, the description is insufficient. It doesn't explain how filters combine (AND/OR), search logic (partial match, case sensitivity), or what the response contains. Context signals show no output schema, so the description should compensate but fails to.

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?

Input schema has 100% coverage with descriptions for all 5 parameters, so baseline is 3. The description adds no extra meaning beyond stating 'optional filters', which is redundant. It doesn't explain combinations or search term matching behavior.

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?

Description states 'Search for quotes with optional filters', clearly indicating the verb and resource. It distinguishes from sibling search tools by specifying the resource is quotes, and from get_quote which retrieves a single quote. However, it lacks specificity about what kind of quotes (e.g., Autotask quotes) and could mention that it returns a list.

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 on when to use this tool vs. alternatives like get_quote or search_quote_items. For example, it doesn't clarify that search is for multiple quotes or when you don't have an ID. The context of optional filters is implied but no explicit when-to-use or when-not-to-use instructions.

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