draft_delete_image_ad_item

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

With no annotations, the description must carry the full burden of behavioral disclosure, but it only says 'Delete a draft image ad item.' It doesn't mention whether the deletion is reversible, whether it's a soft delete, what happens to dependent entities, or any required permissions. For a mutation tool, this is a significant transparency gap.

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, direct sentence with no filler. It's appropriately sized for the tool's simplicity and front-loaded with the key action.

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 one-parameter delete operation, the description is minimally viable: it states what the tool does. However, it lacks any context about the deletion's effect on drafts (e.g., whether deletion is permanent, tied to a draft workflow) or what response to expect. Given no output schema and no annotations, the description is just barely adequate.

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 schema covers the single parameter fully, describing 'id' as 'Draft ad item ID.' The description adds no additional meaning beyond this. Since schema coverage is 100%, a baseline of 3 is appropriate; the description doesn't need to compensate for undocumented parameters.

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 specific verb ('Delete') and resource ('draft image ad item'), making the tool's function clear. It distinguishes from sibling tools like 'delete_image_ad_item' by the 'draft' qualifier, though it doesn't explicitly contrast with non-draft delete variants.

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 usage guidance is provided. There's no mention of when to use this tool versus alternatives (e.g., 'delete_image_ad_item' or other draft delete tools), nor any prerequisites or exclusions. The description relies entirely on the name to convey its scope.

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