unlink

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

Beyond the destructiveHint annotation, the description details behavior: 'Destructive and irreversible', 'Fails safely on directories', 'Use --dry_run to preview', and 'Returns JSON with the removed path'. This adds valuable context.

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 concise (6 sentences) and well-structured, front-loading the core purpose and constraints. Every sentence adds value, with no redundancy.

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 file removal tool, the description covers purpose, destructiveness, behavior on directories, dry-run support, return format, and sibling relationships. It is complete given the lack of an 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 coverage is 100%, so the description adds limited new information. It mentions using --dry_run to preview, which adds context for the dry_run parameter. However, there is a slight inconsistency: the description says 'Remove a single file' but the paths parameter accepts an array, potentially misleading.

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 removes a single file (not directories), which distinguishes it from siblings like rm and rmdir. The verb 'remove/unlink' is specific and the resource is well-defined.

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 provides when to use ('Use to delete individual files by name'), when not to use ('Not for recursive directory removal — use 'rm --recursive'. Not for empty directories — use 'rmdir''), and lists alternatives ('See also 'rm', 'rmdir''). It also mentions dry-run support.

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