List DM drafts

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

No annotations are provided, so the description carries the burden of disclosing behavior. 'List' implies a read-only operation, and 'locally stored' adds storage context, but the description does not mention return format, ordering, or whether deleted statuses are excluded by default. For a simple listing tool this is acceptable but not richly transparent.

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, front-loaded sentence conveys the resource, the local-storage qualifier, and the optional filter. There is no wasted wording or redundancy.

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 tool is simple: one optional parameter, no output schema, and no nested objects. The description covers the core purpose and filtering capability, which is sufficient for a list operation. It does not describe the returned fields, but that is not a significant gap given the tool's low complexity.

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 input schema has 100% description coverage with a clearly described enum-constrained status parameter. The description merely reiterates the optional filter, adding no new semantic detail beyond what the schema already provides, so the baseline of 3 applies.

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 explicitly identifies the resource as 'locally stored DM drafts', making it clear this is about DM drafts specifically. This distinguishes it from sibling tools like list_drafts and list_dm_inbox, and the optional status filter is also mentioned.

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: it lists DM drafts that are locally stored and supports an optional status filter. It does not explicitly name alternatives or exclusions, but the DM-specific naming makes the intended usage clear versus the general list_drafts or list_dm_inbox.

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