autotask_search_opportunities

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

With no annotations, the description must convey behavioral traits. It only states 'search with optional filters', omitting important details like pagination behavior (e.g., default pageSize, possible max results), whether results are sorted, or if filters combine as AND or OR. The agent lacks insight into side effects or limitations.

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 (one sentence). While it avoids verbosity, it is too terse to be informative. It lacks structural elements like bullet points or separate sections for clarity.

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 complexity of a search tool with 4 parameters and no output schema, the description is incomplete. It does not explain return values (e.g., list of opportunities with which fields), error conditions, or how to handle large result sets. The agent is left without crucial context for robust interaction.

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 every parameter already has a definition. The description adds no additional meaning beyond the schema, such as parameter interactions or recommended values. It meets the baseline but provides no enhancement.

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 states 'Search for opportunities with optional filters', which indicates a listing or filtering function. However, it does not distinguish from sibling tools like 'autotask_search_projects' or 'autotask_search_quotes', as all share a similar pattern. It lacks specificity about what 'search' entails compared to 'get' operations.

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_get_opportunity' for individual retrieval or other search tools. The description does not mention use cases, prerequisites, or exclusions.

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