list_conversations

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not mention read-only behavior, pagination behavior (despite page params existing in schema), result scope, or any side effects. The statement 'List all' hints at a complete listing but does not elaborate on potential limits or nuances.

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?

A single sentence that is concise, front-loaded, and free of fluff. It communicates the essential action and resource without wasted words.

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?

The description is minimal for a simple list tool. It does not mention return format, pagination behavior, or how this tool fits into the broader workflow. Even though the schema covers parameters, the lack of annotations and output schema, combined with zero usage context, leaves the description incomplete for an agent to confidently select and invoke the 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 description coverage is 100% (both page and pageSize are described). The tool description adds no extra parameter context, but the baseline of 3 applies given the high coverage.

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 identifies the tool as a list operation on chat conversations/sessions in DreamingAI. While it distinguishes from create/delete/history siblings by verb and resource, it does not explicitly compare to alternatives or clarify scope (e.g., all users vs. current user).

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 provided on when to use this tool versus siblings like get_conversation_history or create_conversation. The description is purely declarative and lacks context about prerequisites, filtering, or use cases.

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