delete_file

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

The description says 'Delete,' which is a destructive action, but the annotations set destructiveHint to false. This is a direct contradiction. The description also does not mention irreversibility, permissions, or side effects beyond the deletion itself.

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 one short, front-loaded sentence with no filler. It is efficient, though its brevity omits important behavioral and usage context that would make it fully helpful.

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 file operation with no output schema, the description should disclose irreversibility and failure behavior. The contradictory destructiveHint makes the tool's safety profile unclear, and while the single-parameter complexity is low, the missing context is still significant.

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 0%, and the description only says 'NXT user-flash file' to hint at what name refers to. It does not specify whether name requires an extension, a path, or any formatting constraints, leaving the only parameter underspecified.

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 a specific verb and resource: 'Delete one NXT user-flash file.' This clearly distinguishes the tool from siblings like read_file, write_file, and list_files.

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 provided about when to use this tool versus alternatives, nor any exclusions or prerequisites. The description does not mention checking file existence with list_files or any conditions under which deletion should be avoided.

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