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 does not mention whether this is a read-only operation, rate limits, or pagination behavior (pageSize parameter hints at pagination but not explicitly). The description is too minimal to compensate for missing annotations.

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 uses front-loaded structure with the key verb and resource. However, it could be more informative without sacrificing conciseness (e.g., mentioning pagination or sorting).

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 has 4 parameters with no required fields, no output schema, and no annotations, the description should provide more context about return format, result set behavior, and interaction with other tools. The minimal description is insufficient for an agent to fully understand the tool's behavior.

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 extra meaning beyond the schema's parameter descriptions. No parameters have enums or nested objects, so the schema is straightforward.

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 says 'Search for opportunities with optional filters,' which identifies the verb/resource. However, it lacks specificity about the scope or behavior (e.g., pagination, result set size) and does not differentiate from sibling search tools like autotask_search_projects or autotask_search_tickets.

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 versus other search tools (e.g., autotask_search_companies). There is no mention of prerequisites, performance considerations, or specific use cases. The description implies that all filters are optional, but does not explain when each filter is appropriate.

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