list_conversations

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

Annotations already provide readOnlyHint:true and openWorldHint:true. The description adds minimal behavioral insight beyond restating the action (list) and clarifying the resource type (inbox messages). It does not disclose pagination, ordering, or output structure, which are important for a list operation with no output schema.

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 sentence with no wasted words. Every term adds value: 'list' for action, 'conversations (inbox messages)' for clarity, and 'for the authenticated user' for scope.

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 zero-parameter, read-only list tool, the description covers the basic purpose but lacks details about the return format, pagination, or ordering. With no output schema, the agent would benefit from additional information about the response structure.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds no parameter information because none exist, which is appropriate.

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 'List conversations (inbox messages) for the authenticated user,' which specifies the verb (list), resource (conversations), and scope (authenticated user). It differentiates from siblings like get_conversation (single) and send_conversation (create) through the plural 'list' and clarification of inbox messages.

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 provides clear context by indicating it lists only the authenticated user's conversations, but does not explicitly state when not to use it or mention alternative tools like get_conversation_unread_count for a count. It meets the threshold for 'clear context, no exclusions'.

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