list_conversations

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds pagination behavior (limit/offset paging) but says nothing about ordering of results, default page size, or whether pages are stable — relevant for a paginated read tool.

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?

Three short sentences, front-loaded with purpose and then the filter surface. Minor redundancy in calling offset both a "page offset" and "non-negative" while the schema already labels it rows-to-skip.

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, zero-required-param list tool with full schema coverage and annotations, this is close to sufficient. The main omission is any hint of result ordering/defaults, notable because there is no output schema to describe the return shape.

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%, so all four parameters are already documented and the baseline is 3. The description restates storeId's accepted identifier forms (matching the schema) but does add one constraint not in the schema: offset must be non-negative.

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?

States a specific verb and resource ("List inbox conversations") that an agent can act on directly. However, it never distinguishes itself from the sibling search_conversations, which is the exact alternative an agent will weigh when deciding how to retrieve conversations.

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 says the filters are "Optional" but gives no when-to-use conditions, no prerequisites, and no pointer to search_conversations or get_conversation as alternatives. The agent must infer that this is the unfiltered/browse path purely from the verb "List".

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