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

The description's 'Delete' aligns with the destructiveHint: true annotation and readOnlyHint: false. However, it does not disclose permanence, cascading effects, or permission requirements, though the destructive annotation covers the core side effect.

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, focused sentence with no filler or redundant wording. It directly communicates the primary operation and identifier.

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 delete operation, the description identifies the target and action, and an output schema exists. However, it lacks usage context and alternative guidance, leaving the agent to infer when this destructive action is appropriate.

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 description adds some meaning to the lone 'selection_key' parameter by indicating it can be a selection key or a creative reference, but it does not specify format, requiredness, or possible ambiguity. Schema coverage for the single parameter is present but shallow.

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'), the resource ('owned creative'), and the identification method ('by selection key or creative reference'). It is concise and distinct from sibling tools that list, get, upload, or confirm creative actions.

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 related creative operations such as abandon_upload, confirm_upload, or list. The description states what it does but not the context or conditions that should trigger its use.

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