Delete File

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

Annotations already declare destructiveHint: true and readOnlyHint: false, so the 'DESTRUCTIVE' warning in the description adds little beyond what structured metadata provides. The description does not contradict the annotations, but it also contributes minimal additional behavioral insight beyond the endpoint URL and repetition of destructiveness.

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 extremely tight—one sentence plus a one-word emphatic warning. There is zero wasted wording and the destructive warning is front-loaded and highly visible. Slightly more useful content could be added, but as-is it is efficiently structured.

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 single-parameter tool with strong annotations and no output schema, the description is mostly adequate. However, it misses opportunities to cover edge-case context like whether the operation is reversible, permission requirements, or whether the deleted file is permanently removed versus moved to trash. Minimal but passable.

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%, and the schema itself thoroughly documents the 'file' parameter, including relative path semantics and allowed directory examples. The description adds nothing about parameters, which is acceptable given the schema covers the bases. This hits the baseline of 3 for high schema coverage.

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?

'Delete a file' uses a clear verb+resource construction and includes the raw HTTP endpoint (DELETE /sdapi/v1/delete-file) which adds precision. It could better distinguish itself from sibling tools like sdnext_delete_image or sdnext_file, but the core 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?

The description provides no guidance on when to use this tool versus alternatives. Given the presence of similar siblings (sdnext_file, sdnext_delete_image, sdnext_upload) that might overlap, an explicit note on file deletion semantics or constraints would help. No when-to-use or when-not-to-use context is offered.

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