search_opportunities

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

Without any annotations, the description must disclose behavioral traits. It only states the search action without mentioning pagination, result limits, ordering, or whether partial matches are supported. The agent gains no insight into how the tool behaves beyond the basic operation.

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 very concise (7 words), but the brevity sacrifices clarity and completeness. While not verbose, it could be more informative without adding much length, e.g., by noting the scope of search.

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 6 optional parameters, no output schema, and no annotations, the description is insufficient. It fails to explain return format, result ordering, or behavior when parameters are omitted (e.g., no query), leaving major gaps for an AI agent.

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 schema provides 100% coverage with parameter descriptions, so the tool description adds no extra semantic value. Baseline of 3 is appropriate as the description does not harm but does not enhance understanding of parameters.

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 it searches for opportunities in GoHighLevel, specifying the resource ('opportunities') and context ('in a pipeline'). However, it does not clarify whether the search is across all pipelines or only when a pipelineId is provided, leaving some ambiguity.

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 given on when to use this tool versus alternatives like 'get_opportunity' for single record retrieval or 'search_contacts' for contacts. It does not mention conditions where other tools should be preferred or excluded.

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