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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing stable ID ordering (deterministic pagination), that contact labels are untrusted user content (injection warning), that messages are not marked read, and the required anonping:read scope. These are exactly the auth, side-effect, and trust-boundary facts an agent needs.

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?

Four short, front-loaded sentences with no filler; the purpose leads and each following clause carries a distinct operational fact. Slightly telegraphic but 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 paginated list tool with no output schema, the description covers scope, ordering guarantees, trust caveats, and read-state behavior. It does not describe the shape of a returned conversation (IDs, participants), which is the only notable gap.

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 100%, so limit and cursor are already documented in the schema. The description adds no syntax or format detail for them; 'Stable ID ordering' only loosely informs cursor reliability, so the baseline 3 applies.

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 (List) and resource (active anonymous and friend conversations) with scope narrowed to the connected account. It is clearly separable from siblings such as receive_messages, get_status, and end_conversation 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?

Usage is implied by the enumeration framing, and 'Does not mark messages read' faintly signals that mark_read is the alternative for read state, but no explicit when-to-use or when-not-to-use condition or named alternative is given.

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