delete_file

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Delete a file' without addressing the destructive nature, irreversibility, permissions required, or behavior on missing files or directories, which is a significant gap for a mutation tool.

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 appropriately sized—one sentence followed by an Args block—with no filler. It is front-loaded with the core action and immediately explains the parameter.

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 delete operation with one parameter and an output schema, the description covers the basics but omits behavioral details such as error handling, whether the operation is permanent, or what happens if the path is a directory. It is adequate but minimal.

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 schema's 'path' parameter has no description, so the tool description adds essential meaning by specifying 'Relative path to the file'. This clarifies that the path is relative and points to a file, compensating well for the 0% 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?

The description states 'Delete a file on WD MyCloud' with a specific verb and resource, clearly identifying the action and target. It distinguishes from sibling tools like delete_directory by specifying 'file' and the device.

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 implies usage for deleting files but offers no explicit guidance on when to use this tool versus alternatives like delete_directory. No exclusions or prerequisites are mentioned, leaving the context to be inferred.

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