Delete a local draft

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds valuable context: it removes copied photos as a side effect, scopes the operation to local data, and clarifies the force parameter behavior when a draft was published. This goes beyond the structured annotation data.

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, directly to the point. The first sentence states the core action, the second adds a crucial boundary and a condition. No wasted words or repetition.

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 simple two-parameter destructive operation with no output schema, the description covers the primary effect, side effects, scope boundary, and a conditional nuance. It is complete enough for an agent to use the tool correctly.

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 50% (only 'force' has a description). The description reinforces the meaning of force by stating when it is needed ('Published drafts need force: true'), adding behavioral semantics. 'draftId' is not elaborated, but its meaning is clear from the tool name and description. The description compensates for the incomplete 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?

The description states a clear action ('Removes') on a specific resource ('a local draft and its copied photos'). It explicitly distinguishes from the Vinted platform ('Does not touch anything on Vinted'), which differentiates it from the sibling tool 'delete_listing' and other listing-related tools.

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 communicates this is for local drafts only, and the phrase 'Does not touch anything on Vinted' implies the alternative for Vinted deletions. It also gives a specific condition ('Published drafts need force: true'), which is a clear usage guideline. However, it does not explicitly name the alternative tool, so it misses the full 5.

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