search_opportunities

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

The description discloses that results are ordered by close date and include both standard and custom fields, giving useful behavioral context. With no annotations provided, this information carries the full burden and is adequate, though it does not mention pagination or error behavior.

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 two concise sentences that directly state the search criteria and result characteristics. No redundant information or filler words, making it easy for an agent to parse quickly.

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 moderate complexity (6 parameters, no output schema, no annotations), the description is sufficient. It covers search criteria, result ordering, and field scope. It does not detail pagination behavior, but that is not essential for a search tool where pageSize and pageNumber parameters are self-explanatory.

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?

All six parameters have individual descriptions in the schema (100% coverage), and the tool description reinforces the role of name, account, and stage filters. The schema descriptions are clear and include examples, adding meaning beyond simple parameter names.

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 action (search for Salesforce opportunities), the search criteria (name, account, stage), and the result characteristics (ordered by close date, includes standard and custom fields). This unambiguously distinguishes it from sibling tools like get_opportunity_details or opportunity_insights.

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 through its name and criteria but does not explicitly say when to use this tool versus alternatives such as execute_soql or search_fields. No exclusions or conditional guidance are provided, so guidance is only implicit.

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