drafts_delete

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

Since no annotations are provided, the description bears full responsibility for behavioral disclosure. It adds transparency by stating it's an 'undocumented session endpoint' and describes automatic timestamp fetching to avoid conflicts. However, it does not mention permanence of deletion, required permissions, or what the boolean output schema indicates.

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 extremely concise: two sentences with no unnecessary words. The first sentence states the purpose, and the second explains the key parameter nuance. It is front-loaded and efficient.

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?

Given the small number of parameters (2), high schema coverage (100%), and presence of an output schema (bool), the description covers the essential behavioral aspects. It notes the undocumented nature and auto-fetching. Minor gaps: no mention of failure conditions or irreversibility, but fairly complete for a simple delete 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 100% schema coverage, baseline is 3. The description adds value by explaining the automatic behavior when client_last_updated_ts is omitted, providing context that the schema alone does not convey.

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 the action ('Delete a draft') and identifies it as an undocumented session endpoint. This verb+resource specification is unambiguous and distinguishes it from sibling tools like drafts_create, drafts_list, and drafts_update.

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 explains when to omit the optional timestamp parameter (to avoid conflict errors) and that it will be auto-fetched. However, it does not explicitly state when to use this tool versus other delete tools (e.g., chat_delete, files_delete) or any prerequisites.

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