Delete

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal the destructive nature and the FS_READONLY requirement, and it clarifies recursive behavior. However, it does not state irreversibility, failure behavior for non-empty directories when recursive=false, or other error cases.

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 extremely concise: two short sentences that each add necessary information. The core behavior is front-loaded, and the prerequisite is stated compactly without waste.

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 two-parameter delete tool, the description covers the main behavior, the recursive edge case, and the required configuration flag. An output schema exists, so return values need not be explained. It could mention error behavior, but the essentials for invoking the tool correctly are present.

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 description coverage is 0%, so the description must clarify parameters. It adds meaning to 'recursive' by specifying that it enables directory deletion. However, 'path' is left largely implicit as the file or directory to delete, with no additional guidance on formats or edge cases.

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 a specific action ('Delete') and target ('a file, or a directory'), with the condition for directories ('if recursive=True'). It clearly identifies what the tool does, though it does not explicitly differentiate itself from sibling tools such as move or copy.

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 provides clear context: use it to delete files, or directories when recursive is true. It also gives a prerequisite ('Requires FS_READONLY=false'). It does not explicitly state when not to use it or name alternatives, but the purpose is unambiguous.

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