Create GoHighLevel Opportunity

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

Description explicitly labels it as a 'Write operation' and warns against live use, aligning with annotations (readOnlyHint=false). Does not disclose potential side effects like workflow triggers, but sufficient for standard creation.

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?

Two sentences, no fluff. Essential information front-loaded. Every sentence adds value.

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?

Missing details on return format, default behaviors for optional fields, and clarification of 'extra' object. No output schema. For a complex tool with 11 parameters, more context would help.

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 covers 64% of parameters with descriptions. Description adds no parameter-level details beyond schema. Several parameters lack descriptions in both schema and description, so baseline at coverage >50% is appropriate.

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?

Clearly states verb ('create'), resource ('opportunity'), and API endpoint ('POST /opportunities/'). Distinguishes from sibling tools like search, update, delete.

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?

Provides clear warning against running on live data without approval, but lacks explicit comparison to alternatives like update or search. The warning alone is helpful guidance.

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