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 genuinely non-obvious behavior: the tool ignores any date range passed to it and returns a point-in-time snapshot, which prevents an agent from expecting filtering. It does not describe the shape or units of the returned counts.

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, no filler, and the most important constraint ('snapshot, not a period: it ignores any date range') is placed last as a sharp caveat after the primary purpose. Every clause 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?

With no output schema, the description carries the burden of conveying returns, and it does name the four metrics produced. Combined with annotations covering the safety profile and a fully documented single parameter, an agent has enough to call it correctly, though it never states the numeric/structured form of the response.

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?

There is a single optional 'fields' parameter and schema coverage is 100%, with the enum values documented in the schema, so the baseline is 3. The description's mention of open/unattended/unassigned/pending loosely mirrors the enum but adds no syntax or defaulting guidance beyond the schema.

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 exactly what is computed — the count of currently open conversations, broken out into unattended, unassigned and pending — with the resource and the scope ('right now') made explicit. The 'snapshot, not a period' framing distinguishes it from the period-based reporting siblings such as get_conversation_report and list_all_conversation_statistics without the agent needing to open a 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?

It gives clear context for when this tool is the right choice: a live snapshot as opposed to a period-based report, reinforced by 'it ignores any date range'. It stops short of naming an alternative tool or stating an explicit when-not-to-use, so it does not reach the top of the scale.

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