drafts_delete

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

Describes the undocumented session endpoint nature and the automatic timestamp fetching, but does not detail side effects or mutation consequences. With no annotations, the description carries the transparency burden but omits some behavioral context.

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?

Two sentences, front-loaded with purpose, concise and to the point. Every sentence adds value.

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?

Covers the essential purpose and parameter behavior. Output schema exists so return values are documented. Adequate for a simple delete operation.

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?

Adds significant meaning beyond the input schema: explains that draft_id is required and client_last_updated_ts is optional with automatic retrieval from drafts.list if omitted. Schema has 0% coverage, so description compensates fully.

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 the resource. It distinguishes itself from sibling tools like drafts_create, drafts_update, and drafts_list.

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?

Provides guidance on handling the optional client_last_updated_ts parameter, explaining the automatic fallback to avoid conflict errors. However, it does not explicitly contrast with alternative actions.

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