autotask_search_quotes

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

With no annotations, the description must disclose behavioral traits. It only states the tool searches, but does not indicate whether it is read-only, if pagination is supported, what the response format is, or any side effects. The minimal description leaves significant behavioral ambiguity.

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 extremely concise (4 words) but at the cost of informativeness. It essentially restates the tool name, providing little beyond the name. Conciseness should not sacrifice substance; here it is underspecified.

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 5 optional parameters and no output schema, the description lacks completeness. It does not explain how filters combine, default page size, maximum results, or what the returned data contains. A comprehensive description would include these details for a search endpoint.

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 input schema provides 100% coverage with descriptions for all 5 parameters. The description adds no additional meaning beyond 'optional filters', which is already implied by the schema. Thus it meets the baseline but offers no extra value.

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 quotes with optional filters, which is specific and distinct from sibling tools like autotask_search_quote_items that search for quote items. However, it does not explicitly differentiate from other search tools (e.g., search_opportunities), but the verb 'search' and resource 'quotes' are unambiguous.

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, such as autotask_search_quote_items or autotask_get_quote. The description does not mention that all parameters are optional, nor does it explain the default behavior or typical use cases.

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