List all drafts

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

The readOnlyHint annotation already declares safety, and the description adds the scope 'across chats' which clarifies the returned data. However, it does not disclose pagination behavior, whether drafts are returned in any particular order, or any specifics about the structure of the returned drafts.

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 that immediately and clearly states the tool's purpose. No extraneous words or repetition exist.

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?

Despite its simplicity, the tool has an undocumented accountId parameter and no output schema. The description fails to clarify the parameter's role, and without any return format details, the agent cannot fully anticipate the tool's behavior.

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?

The schema has one parameter (accountId) with zero description coverage. The description does not mention this parameter at all, leaving its purpose and relationship to the described functionality completely unexplained.

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 ('Return') and identifies the resource ('all dialog drafts') and scope ('across chats'). It clearly distinguishes itself from mutation siblings like save_draft and clear_draft, and from other list tools like list_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?

No guidance is provided on when to use this tool versus alternatives such as save_draft or clear_draft. The read-only nature is implicit, but there is no explicit mention of exclusions or preferred context.

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