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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely new fact — the note is 'visible to the agency's team' — but 'additive' largely restates the non-destructive/non-idempotent hints and nothing is said about auth needs or the effect of repeated calls.

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 tight sentences with the action front-loaded and the rationale trailing; no filler or repetition. Slightly under-specified for the parameter surface, but structurally efficient.

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 a low-complexity mutation tool with annotations and no output schema, the description covers the what and a bit of the why. However, with 0% schema coverage and an undocumented 'confirm' flag, it leaves real gaps an agent would need to close before invoking 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?

Schema description coverage is 0% across 4 parameters, so the description carries the full burden. It only implies that a note attaches to a contact (gesturing at contact_id); location_id, the note string, and especially the unexplained 'confirm' boolean receive no semantic treatment at all.

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 a specific verb and resource ('Add a note to a HighLevel contact'), and the note-to-contact framing is inherently distinct from siblings like highlevel_update_opportunity or highlevel_create_prospect. It never explicitly names or differentiates itself from any sibling, so it falls short of a 5.

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?

'Useful for recording what was agreed or what you changed' gives an implied usage scenario but no explicit when-to-use, when-not-to-use, or named alternatives. An agent gets a hint about intent but no routing guidance against the other highlevel_* tools.

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