Delete media many

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description earns credit for noting per-id outcome reporting, which hints at partial-failure behavior, but it never states atomicity, irreversibility, or any confirm/rate-limit requirements for a destructive batch call.

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 clause with zero padding. It is tight but borders on underspecified for a destructive batch operation.

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 batch tool with no output schema and no annotations gap to fill on safety, the description should disclose batch limits and what a 'per-id outcome' looks like (partial success? errors inline?). It signals the shape of the result but not enough to call it 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?

Schema coverage is 0% for the single mediaIds parameter, and the description says nothing about it — no format (opaque ID vs URL), no maximum batch size, no note that minItems is 1. The schema carries a bare array type and nothing else.

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') and adds an outcome clause ('reports per-id outcomes'). 'Several' implicitly distinguishes it from the singular delete_media sibling, though the sibling is never named.

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 word 'several' implies this is the batch path versus delete_media for one item, but there is no explicit when-to-use, no exclusion, and no prerequisite (e.g., whether IDs must exist or whether this cascades to posts referencing the media).

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