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

No annotations provided, so description carries full burden. It discloses sort order (newest first), return fields (compact list with specific fields), and optional filters. Missing details on pagination behavior, rate limits, or auth requirements, but for a read-only list tool, the transparency is adequate.

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, each dense with information. First sentence gives purpose and sort order; second covers optional filters and return fields. No redundant or superfluous words. Excellent front-loading of key info.

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?

Given no output schema, description explains return fields. Covers purpose, filters, sort, and output. Missing mention of pagination mechanics (e.g., using limit for page size, but no cursor). Slight gap but otherwise complete for a simple 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 coverage is 100%, but description adds value by clarifying the 'search' parameter (free-text on contact name/email and last message) and stating the default for 'limit' (100). The enum for 'status' is replicated but schema already lists values. Overall, description enhances parameter understanding 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 clearly states the verb 'List', the resource 'conversations', and the context (workspace's support conversations, agent/inbox view). It distinguishes from siblings like get_conversation (single) and resolve_conversation (action) by specifying the listing nature and sort order.

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?

The description implies when to use (when needing a list of conversations) and specifies optional filters (status, search). However, it does not explicitly mention when not to use or compare to the sibling 'search' tool, which may be for more extensive search. Lacks explicit exclusions or alternatives.

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