enrich_opportunity

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

With no annotations, the description carries the full burden of disclosing behavior. It does not state whether the operation is read-only, modifies the opportunity, or has side effects, and it lacks any mention of authorization, rate limits, or data sourcing.

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, focused sentence with no redundant content. It efficiently conveys the tool's core function.

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?

The description explains the purpose but does not mention the return value, output structure, or error behavior. Since there is no output schema, more detail about what the enriched output looks like would improve completeness for an 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?

Schema coverage is 100% with descriptions for all three parameters. The descriptions are largely tautological ('The ID of the Salesforce opportunity to enrich with intelligence'), but they do convey basic meaning and defaults for the boolean flags. No extra format or constraint details are provided.

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 a specific action ('Enrich an opportunity') and the resource ('opportunity'), with a clear outcome (market intelligence, industry insights, strategic recommendations). However, it does not differentiate from overlapping siblings like 'opportunity_insights' or 'find_similar_opportunities'.

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 'opportunity_insights', 'find_similar_opportunities', or 'generate_business_case'. The description mentions based on similar deal patterns and best practices but does not specify conditions or exclusions.

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