delete_file

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

With no annotations, the description carries the full burden for behavioral disclosure. It simply says 'Delete a file' and does not mention whether deletion is permanent, irreversible, permission-gated, or destructive to any related state. For a destructive operation, more transparency is required.

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, short sentence with no filler. It states the verb, resource, and a key scope condition in the fewest possible words.

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?

This is a destructive mutation tool with no annotations, no output schema, and no parameter documentation. The description is too brief to convey important operational context such as permanence, error behavior, workspace prerequisites, or file path conventions. It falls below minimum viability for safe automatic invocation.

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 has 0% description coverage and the description adds no parameter details. It does not explain how 'path' should be formatted, whether it is absolute or workspace-relative, or what 'workspace_id' refers to. The basic property titles provide some meaning, but the description does not compensate for the schema's lack of documentation.

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 uses a specific verb-and-resource pair ('Delete a file') and adds the scope 'within an active workspace.' This is enough to distinguish the tool from siblings like delete_workspace or create_file, so an agent can tell what the tool is for immediately.

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 about when to use this tool versus alternatives. The phrase 'within an active workspace' implies an environmental prerequisite, but it does not instruct an agent about the right context for file deletion or exclude sibling tools like delete_workspace.

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