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

Annotations declare the mutation posture (readOnlyHint=false, destructiveHint=false, idempotentHint=false) but say nothing about the two-phase confirm/preview flow, which the description discloses as the default behavior. It omits what happens on duplicate opportunities or failure handling, keeping it short of a 5.

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?

Three tight sentences with no filler; the core create action and its attachments are front-loaded, followed by dependency sourcing and the preview instruction in priority order.

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?

For an 8-parameter mutation tool with no output schema and only 50% param coverage, the description covers the critical safety workflow and ID provenance but leaves the required location_id and the monetary_value/status semantics unexplained. Adequate but with clear gaps.

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 50% and the description fills some of that gap by naming the source tools for pipeline_id, pipeline_stage_id and contact_id, and by framing confirm's purpose. However, required 'location_id' and optional 'monetary_value' and 'status' are undocumented in both schema and description, leaving real gaps.

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?

States a specific verb and resource ('Create an opportunity') and disambiguates the term with a parenthetical definition ('a potential job'), plus the pipeline and contact attachment constraints. An agent can distinguish it from highlevel_update_opportunity and highlevel_opportunities without opening any schema.

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?

Gives clear preconditions and routes the agent to the right siblings for ID acquisition (highlevel_pipelines, highlevel_find_contact, highlevel_create_prospect) and describes the preview-first call pattern. It does not state when NOT to use it (e.g. vs. updating an existing opportunity), so it falls short of full exclusion guidance.

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