delete_media

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

The description discloses that deletion is cascading (removes files and thumbnails), which is key behavioral context. However, without annotations, it omits details like permission requirements, reversibility, or rate limits. The transparency is adequate but not thorough.

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 with no waste. It efficiently conveys the core action and scope. A slightly more structured format (e.g., listing affected resources) could improve scannability but is not essential.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the basic function. However, it lacks context about what a 'generation' is, potential side effects, and whether the operation is reversible. It is minimally complete.

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?

With 0% schema description coverage, the parameter 'generation_id' is entirely undocumented in both schema and description. The description fails to explain what a generation ID is or how to obtain it, adding no value beyond the field name.

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') and the resource ('a generation together with its files and thumbnails'), making the purpose specific and unambiguous. No sibling tool has a similar verb, so differentiation is inherent.

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 (e.g., using get_media to inspect before deletion) or when not to use it. The description lacks any context about prerequisites or contraindications.

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