Get GHL Opportunity

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds little beyond 'details', with no extra context about return structure, possible errors, or rate limits. For a simple get operation, this is adequate but not enriched.

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, front-loaded sentence with no filler. 'Get details of a specific opportunity/deal.' is compact and directly readable.

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 tool is simple with only one required parameter, complete schema documentation, and strong annotations. The description effectively communicates the core function, and while it doesn't detail the return fields (no output schema), it's sufficient for a get-by-ID operation in this context.

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 description coverage is 100% for the single parameter 'opportunityId' described as 'Opportunity ID'. The description does not add any additional meaning or format beyond the schema, so it sits at the baseline of 3.

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 'Get details of a specific opportunity/deal' clearly identifies the verb (Get), resource (opportunity/deal), and specificity (specific). It distinguishes from sibling tools like ghl_search_opportunities, ghl_create_opportunity, and ghl_update_opportunity by focusing on a single known entity.

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 doesn't mention that this is the tool to use when you have an opportunityId, nor does it point to ghl_search_opportunities for finding opportunities by criteria. There are no exclusions or alternative references.

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