autotask_search_opportunities

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 states 'with optional filters' and does not mention that results are paginated, the default/max page size (already in schema), what fields are returned, or any side effects. For a search tool, this is insufficient transparency.

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 but lacks structure or detail. While not verbose, it is too brief to be considered optimally helpful; more information could be added without sacrificing conciseness.

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's complexity (optional filters, no output schema), the description should explain what the search returns, pagination behavior, and how filters combine. It covers none of this, leaving the agent with incomplete information to use the tool effectively.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond 'optional filters'. The schema already explains each parameter; the description does not provide usage context or examples. Therefore, it meets baseline but adds 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 verb 'Search' and the resource 'opportunities', and mentions optional filters. It distinguishes from sibling tools that are create/update/get, but there are many other search tools, so differentiation is implicit. The purpose is clear but could be more specific about what 'search' entails.

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 provides no guidance on when to use this tool versus alternative search or retrieve tools. It does not mention prerequisites, context, or exclude cases. With numerous sibling tools (e.g., autotask_search_companies), the lack of usage guidelines is a significant gap.

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