Client conversations

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so safety and idempotency are covered structurally. The description adds two real facts beyond that: newest-first ordering and the panel-enablement prerequisite. It says nothing about pagination semantics (how to page past the 30-item cap) or what a conversation record contains.

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 short sentences with zero filler; the resource and its ordering come first, and the enablement constraint follows. Every clause carries information an agent would otherwise have to guess.

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 simple read-only paginated list, annotations and the schema carry most of the load. Still, with no output schema, the description could say what a conversation object contains, and it never clarifies the relationship to chat_messages, which is the most likely source of a wrong tool choice.

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% with two simple pagination parameters (limit, offset) that carry defaults and bounds. The description adds no interpretation beyond the schema, so baseline 3 applies – nothing is missing, but nothing extra is contributed.

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?

Names the resource (client chat conversations) and its ordering (newest first), which is enough to know this returns a conversation list rather than messages. It stops short of differentiating itself from the sibling chat_messages tool, so an agent cannot tell from the description alone which of the two to call for a given need.

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?

"Works only where the panel has client chat enabled" is a useful precondition, effectively a when-not-available rule. However, there is no guidance on when to choose this over chat_messages or chat_quick_actions, leaving the choice to inference from names.

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