autotask_search_products

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

No annotations are provided, so description carries full burden. It mentions optional filters but does not disclose pagination behavior beyond the pageSize parameter (default 25, max 100) already documented in schema. No mention of rate limits or authorization requirements.

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 short and to the point, using only 7 words. It is front-loaded with action and resource. However, being too concise may omit useful context like result format or typical use cases.

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 3 optional parameters and no output schema, the description is somewhat complete but lacks information on how results are returned (e.g., list format, pagination with pageSize). For a search tool, describing the return structure would be helpful.

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%, and the description adds minimal value by stating 'optional filters'. The schema already describes each parameter well. However, the description does not explain searchTerm behavior (e.g., is it exact match or fuzzy?).

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 products with optional filters, using the specific verb 'search' and resource 'products'. It distinguishes from sibling 'get_product' which retrieves a single product. However, it could be more explicit about what 'products' means in this context.

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 when needing to find products, but no guidance on when not to use or alternative tools. Among siblings, 'autotask_get_product' exists for retrieving a single product, but the description does not mention this distinction.

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