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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the basic safety profile. The description provides no additional behavioral context—e.g., whether deletion is permanent, cascades to associated data, affects other resources, or requires special permissions. The description does not contradict the annotations but adds negligible value beyond them.

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?

While extremely short, the description is under-specified rather than concisely informative. The single line 'DELETE /v1/media/{id}' conveys the HTTP endpoint but omits essential context. It is not front-loaded with useful information because it contains no natural-language explanation.

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?

With no description of the media resource, the effects of deletion, or any return/error behavior, the tool is not self-contained. Even with an output schema present, an agent cannot confidently use this tool without inferring meaning from the resource name and sibling context. The description fails to provide minimal domain grounding.

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 only 50% (workspaceId has a description, but path.id has none). The tool description adds no parameter-level explanation, so the meaning of the required 'id' field remains entirely undocumented. It does not compensate for the schema gaps.

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 is essentially a tautology: 'DELETE /v1/media/{id}' restates the tool's name and HTTP method without explaining what media is or what deletion entails. It does identify the resource (media) and the action (delete) but provides no domain-specific clarification, and it does not distinguish this from sibling delete tools like delete_posts_id or delete_post_content beyond the resource name.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions (e.g., ownership, permissions beyond the workspace check), or scenarios where other delete tools are more appropriate. An agent has no context to decide between this and sibling delete operations.

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