delete_media_by_media_id

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

The description adds no behavioral details beyond the annotations, which already indicate destructive and idempotent behavior. It doesn't mention permanence, side effects, or authorization requirements. The endpoint is provided, but that's not behavioral. The description does not contradict the annotations.

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 very concise, using three short lines. It is front-loaded with the action and resource, and the parameter is listed. There is no unnecessary content or fluff, making it efficient.

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 single-parameter delete operation, the description is adequate but minimal. It lacks usage context, error handling, or return value explanation, though an output schema exists. Given the destructive nature, a note on permanence or consequences would improve completeness.

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 only parameter, media_id, is described as 'Media ID' which is identical to the schema title and adds no semantic meaning. With 0% schema description coverage, the description fails to clarify what constitutes a valid media ID (e.g., UUID format, where to obtain it, or any constraints).

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 and resource: 'Delete media item.' It also includes the HTTP endpoint, which is specific and distinguishes it from other delete_* tools that target different resources (issues, requests, users, etc.). The purpose is unambiguous.

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 given on when to use this tool versus other delete tools or under what conditions. It doesn't mention any prerequisites, scenarios, or exclusions. The agent must infer usage solely from the name and action.

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