Delete media many

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clarifies that deletion is destructive and that results are reported per id, which is helpful. However, it omits whether deletion is irreversible, how partial failures are handled, or any auth/permission requirements.

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?

A single, front-loaded sentence with no filler. Every word carries meaning: the action, the batch scope, and the response behavior.

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 tool with no annotations and no output schema, this is only minimally complete. It states the core behavior and the fact of per-id reporting, but leaves the outcome format, partial failure semantics, and permanence of deletion unexplained.

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 description coverage is 0%, so the description must compensate. It connects mediaIds to 'media items', giving minimal semantic grounding beyond the property name. It does not explain ID format, whether invalid IDs cause errors, or how the per-id outcomes map to the request ordering.

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?

States a specific verb and resource: 'Delete several media items'. The batch scope ('several') and the per-id outcome reporting distinguish it clearly from the sibling delete_media tool. An agent can tell what it does without inspecting the schema.

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 phrase 'Delete several media items' implies it is for batch deletion, which is useful but not explicit. It does not mention when to use this instead of delete_media, nor does it state any exclusions or failure conditions.

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