draft_delete_placement

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action 'delete' without revealing whether deletion is permanent, cascades to related entities, requires special permissions, or what happens if the placement is not in draft status. Critical side-effect information is missing.

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 a single, concise sentence that immediately states the action and resource. Every word contributes to meaning, with no filler or redundant information. Perfectly sized for a simple tool.

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 single-parameter delete tool, the description is minimally adequate but lacks important context. It does not clarify what 'draft placement' means in relation to the draft workflow, nor does it mention permanence, side effects, or error behavior. Given the simple parameter set and absence of output schema, a middle score is justified.

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 already documents the only parameter 'id' with the description 'Draft placement ID', achieving 100% schema coverage. The description adds no additional semantic meaning beyond this, so a baseline score of 3 is appropriate.

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 'Delete a draft placement' uses a specific verb ('Delete') and a specific resource ('draft placement'), clearly distinguishing it from sibling tools like 'delete_placement' or 'vast_delete_placement' via the 'draft' qualifier. It is unambiguous about what the tool does.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not state that this is for draft placements only, nor does it mention the existence of non-draft deletion tools or any conditions/preconditions. The user is left to infer usage from the name.

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