delete_conversation_draft

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

With no annotations, the description carries the full burden and does disclose the important trait that the handler does not check conversation access and only touches the caller's own drafts, plus the DELETE endpoint. It stops short of saying whether deletion is idempotent or what is returned on success/failure.

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 core scope statement and the access caveat are front-loaded and useful, but the leading line simply repeats the tool name and the trailing endpoint/tag metadata is operational filler rather than guidance for an agent.

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?

For a two-parameter, fully-described mutation tool with no output schema, the definition covers scope, permission semantics, and the optional-parameter effect. Only the post-deletion outcome (idempotency, errors, return value) is left unaddressed.

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?

Schema coverage is 100% and the schema already documents both parameters, including the enum values and the 'omit to delete all types' behavior. The description's restatement of the type-omission rule adds marginal value beyond the schema.

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?

States a specific verb and resource ('Deletes the caller's draft for a conversation') and scopes it to the caller, which distinguishes it from upsert_conversation_draft and the other delete_* siblings that act on different resources.

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 conditional behavior ('Without `type`, drafts of every type are deleted') implies when the optional parameter matters, but there is no explicit when-to-use guidance, no stated alternative, and no mention of what happens if no draft exists.

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