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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context (newest-first ordering, unread counts), but omits pagination behavior and what fields each conversation carries, which matters since there is no output schema.

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 sentences, front-loaded with the core action and scope before the rationale. The second sentence is slightly promotional but still earns its place as usage guidance; no wasted filler.

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 read-only list tool with no output schema, the description conveys the shape of results (conversations with unread counts, ordered). It stops short of explaining limit/contact_id semantics or pagination, so it is adequate but incomplete against a 4-parameter, 50%-coverage schema.

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 only 50%: query and location_id have descriptions, while limit and contact_id are undocumented. The description mentions no parameters at all, so it fails to compensate for the gap and leaves contact_id's filtering role unexplained.

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 ("List recent conversations in a HighLevel sub-account") plus ordering (newest first) and an unread-count dimension. It is clear what the tool returns, though it does not explicitly distinguish itself from the sibling highlevel_read_conversation.

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?

It gives a concrete usage scenario ("answer 'who is waiting on us'"), which is better than none. However, it never names an alternative or a when-not condition — e.g., that highlevel_read_conversation fetches a single thread or highlevel_send_message is for replying — so the agent must infer routing.

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