List Saved-Messages sub-dialogs

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

The annotations already declare readOnlyHint and openWorldHint, so the bar for added disclosure is lower. The description contributes the domain-specific behavior that these sub-dialogs are groupings by origin peer, which helps the agent understand the result semantics. It does not contradict the annotations.

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, front-loaded sentence with no redundant wording. It efficiently communicates the core purpose and a key distinguishing detail.

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 covers the essential 'what' but leaves out important contextual details like the effect of limit and excludePinned, especially given there is no output schema. The openWorldHint and parameter schema partially compensate, but the description alone is only minimally sufficient for an agent to correctly 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?

With 0% schema description coverage and three parameters (limit, accountId, excludePinned), the description provides no explanation of their meaning, behavior, or defaults. The burden falls entirely on the parameter names, which the description does not support.

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 uses a specific verb 'List' and clearly identifies the resource as 'forum-style sub-dialogs inside Saved Messages', with an explanatory clause about grouping by origin peer. This distinguishes it from generic dialog listing tools like list_dialogs.

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 this tool—when you need the sub-dialogs in Saved Messages—but it doesn't provide explicit exclusions or alternative tool references. The context is clear enough for typical use, but it lacks a when-not-to-use statement.

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