ghl_opportunity_create

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Create an opportunity' without mentioning side effects, permissions, reversibility, failure modes, or what data is returned. This is a significant gap for a mutating 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 extremely short but under-specified, providing no value beyond a truncated phrase. It is not concise in an informative way; it is simply insufficient for a tool with 12 parameters.

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 (12 parameters, no output schema, no annotations), the description is inadequate. It fails to address return values, prerequisites, side effects, or how this create operation differs from others. The description is a bare minimum that does not help an agent select or invoke the tool correctly.

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 provides detailed descriptions for all 12 parameters, achieving 100% coverage. The description adds no parameter-specific information, but the schema fully documents meaning, so a baseline of 3 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?

The description clearly states a specific action ('Create') on a specific resource ('an opportunity'). It distinguishes from sibling tools like ghl_opportunity_get/update/delete via the verb, though it lacks any additional context about what an opportunity is or what creating entails.

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 about when to use this tool versus alternatives. The verb 'create' implies usage for new opportunities, but there are no explicit conditions, prerequisites, or comparisons with related tools such as ghl_opportunity_update.

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