list_all_contact_conversations

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

With no annotations provided, the description must disclose behavioral traits. It only says 'List all conversations' without mentioning whether it is read-only, requires authentication, has pagination, or any side effects. This leaves significant ambiguity about its operation.

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?

The description is a single concise sentence with no extraneous words. However, it could have included qualifiers like 'for a contact' without sacrificing conciseness.

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 the lack of output schema and annotations, the description should clarify the scope (e.g., all conversations for a specific contact or across the account). It does not mention return format or pagination, leaving the agent underinformed.

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 are no parameters in the schema, so the description does not need to clarify them. The description states the action (list) and resource (conversations), which suffices for a parameterless tool.

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 'List all conversations' clearly indicates the action and resource, but it lacks specificity. The tool name includes 'contact_conversations' suggesting scope per contact, yet the description omits this, making it indistinguishable from similar tools like 'list_all_conversations' or 'conversation_list'.

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?

No guidance is given on when to use this tool versus its many siblings, such as 'get_single_conversation' or 'list_all_conversation_messages'. There are no context cues or alternatives mentioned.

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