delete_audio_creative

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

The description is a tautology of the tool name, adding no behavioral details such as permanence, side effects, or required permissions. With no annotations provided, the description fails to convey anything beyond the action itself.

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 one-sentence description is brief but redundant, essentially restating the tool name. It lacks structure and doesn't earn its place by adding information.

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 tool, the description is minimal but still missing important context like whether deletion is permanent, cascades to references, or has any restrictions. No annotations or output schema compensate.

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 fully describes the single 'id' parameter with a description, so baseline is 3. The description adds no parameter semantics or usage details 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?

The description uses the specific verb 'Delete' and names the resource 'audio creative', clearly distinguishing it from sibling delete tools for other creative types (e.g., delete_video_creative, delete_rich_media_creative).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that audio creatives are a specific type, nor does it reference the generic delete_creative tool or any prerequisites.

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