Delete Media

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

Annotations already flag destructiveHint/openWorldHint/non-idempotent, but the description adds real substance: the delete is deferred (recoverable via Recently Deleted until a restore window closes), the exact permission scopes required, the confirm gate, and a side-effect warning about access sharing, notifications, and charges. This is far beyond what the annotations disclose.

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 purpose and destructive lifecycle are front-loaded in the first sentence, which is the highest-value content. The permission section is lengthy boilerplate with code blocks, but it is structured and arguably necessary for authorization correctness.

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 destructive mutation with no output schema, it covers the essentials: auth requirements, the confirm gate, recovery semantics, and side effects. Only minor gaps remain (error/not-found behavior, what the response returns).

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 100% and all three parameters are described in the schema, so the schema carries the load. The description only reinforces the confirm=true requirement already documented on the confirm property; it adds no syntax or format detail for media_hashed_id or account.

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?

Specific verb+resource with the full lifecycle spelled out: delete, move to Recently Deleted, restore until the window ends, then permanent purge. This distinguishes it semantically from archive_media and restore_media, though it never names those siblings explicitly.

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 gives prerequisites (required permissions, confirm=true) but does not state when to choose this over archive_media, delete_media_extended_audio_description, or other adjacent delete/restore siblings. Usage is implied by the mutation name rather than explicitly routed.

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