deleteFile

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

Annotations mark it as destructive, and the description adds that it uses VS Code's trash when connected with a native fs fallback. However, it does not disclose other behaviors like permission needs or effects on open files.

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?

Two sentences with no extraneous words. The action and key behavior are front-loaded, making it efficient for an agent to parse.

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 deletion tool with three parameters and no output schema, the description covers the core behavior and the trash fallback, which is important for understanding side effects. It lacks return value info but that is acceptable without output schema.

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 has 100% coverage for all three parameters, so the description adds no extra meaning beyond the schema descriptions. The mention of 'recursive' and 'useTrash' aligns with schema but does not enrich it.

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 clearly states the tool deletes files or directories, specifying both workspace and absolute paths. It distinguishes from siblings like renameFile or createFile by focusing solely on deletion.

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 on when to use this tool versus alternatives. No prerequisites (e.g., file existence) or conditions (e.g., file not open) are mentioned, leaving the agent to infer context.

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