strapi_delete_media

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action ('delete') without mentioning permanence, side effects on entries referencing the file, or error handling. These gaps are material for a destructive operation.

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, direct sentence with no superfluous words. It is front-loaded with the action and resource, making it easy to scan and understand.

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 fully-described parameter, no output schema), the description is minimally adequate. However, it lacks context about the behavioral consequences of deletion and does not explain what the response will look like, which would be expected for a complete description.

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 100% — the fileId parameter is already described as 'Numeric Strapi upload file id.' The tool description adds no additional meaning beyond the schema, simply restating 'by file id.' Per the rubric, high coverage yields a baseline of 3.

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 states exactly what the tool does: 'Delete a Strapi Media Library file by file id.' It uses a specific verb and resource, and clarifies the key parameter (file id), which distinguishes it from sibling tools like strapi_delete_entry (which deletes entries) and media update tools.

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 specify scenarios, prerequisites, or mention that related tools (e.g., strapi_update_media_info) are for modification rather than deletion. The description is purely functional and lacks usage context.

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