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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real value beyond those: newest-first ordering, an unread count in the result, and sub-account scoping. It omits pagination behavior despite the limit parameter.

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 tightly constructed sentences with the core action front-loaded. The second sentence is mildly rhetorical but does communicate the business motivation, so it mostly earns its place.

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?

No output schema exists, so the description carries the burden of describing the return — it gives ordering and unread counts but not the shape of each conversation. Filter parameters also go unexplained, leaving the definition adequate but not complete for a 4-parameter list tool.

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 only 50% (location_id and query are documented, limit and contact_id are bare). The description mentions 'sub-account' vaguely but never explains limit, query, or contact_id, so it fails to compensate for the documentation gap.

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 (list conversations) with scope (HighLevel sub-account) and ordering (newest first), plus the notable detail that it returns unread counts. This clearly separates it from highlevel_read_conversation and highlevel_send_message, though it never names those siblings explicitly.

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?

Provides a use case ('who is waiting on us' / unanswered enquiries) which implies when to reach for it. However it offers no exclusions and does not point to highlevel_read_conversation for drilling into a single thread, so the routing guidance is implied rather than explicit.

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