delete

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

With no annotations provided, the description fully bears the burden of disclosure. It details statuses ('deleted', 'would_delete', 'not_found'), dry-run behavior, symlink handling (deletes link, not target), and cache eviction. This is comprehensive for a simple deletion 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 three sentences long, starting with the core purpose, then usage guidelines, then detailed statuses and constraints. Every sentence adds essential information, with no wasted 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?

Given the tool's low complexity (2 parameters, simple file deletion) and the presence of an output schema, the description covers all necessary behavioral aspects: what happens on success, failure, dry-run, and symlinks. No gaps remain.

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 input schema covers both parameters with 100% description coverage. The description adds value beyond the schema by introducing cache eviction context, status codes for dry-run, and the 'one path only' constraint. This enriches the agent's understanding without being redundant.

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 'Delete one file or symlink and evict its cache entries.' It specifies the action (delete), the resource (file or symlink), and additional behavior (cache eviction). It distinguishes from sibling tools by noting constraints like 'one path only — no globs, no recursion, no real-directory deletes.'

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 explicitly advises 'Use this for explicit single-path removal instead of shelling out,' providing a clear usage context. It also lists constraints that indicate when not to use this tool (directories, globs, recursion). However, it does not explicitly mention alternative sibling tools for those cases.

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