ghl_opportunity_upsert

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

Beyond annotations (readOnlyHint=false, etc.), the description only restates the tool's purpose. It does not disclose behavioral traits like what happens when an ID is provided (update) vs. omitted (create), required fields, or potential side effects. The openWorldHint suggests side effects, but description adds no clarification.

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 (two lines plus endpoint/scopes), but it omits important context such as usage guidelines and behavioral details. While brevity is positive, the lack of essential information prevents it from being well-structured or fully informative.

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's complexity (multiple parameters, nested objects, no output schema), the description is too minimal. It does not explain return values, error conditions, or behavior for missing required fields. Annotations partially compensate but are insufficient for full contextual completeness.

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 input schema has 100% parameter description coverage, so the baseline is 3. The description adds no further parameter meaning beyond what the schema provides, thus it meets the baseline without enhancement.

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 'Upsert Opportunity' and the endpoint, clearly indicating it creates or updates an opportunity. However, it does not distinguish itself from sibling tools like ghl_opportunity_create or ghl_opportunity_update, leaving ambiguity about when to use upsert versus separate create/update actions.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as requiring an existing opportunity ID for updates, or scenarios where upsert is preferred over separate create/update calls.

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