remove_file

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

The description implies destructive behavior (removal) but does not elaborate on permanence, recursion, or error handling. While the action is clear, additional details like 'permanently deletes' or 'requires write permissions' would improve transparency.

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 and front-loaded with purpose, followed by a usage example. However, the structure could be improved by including all parameters in the description.

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 simplicity and the existence of an output schema (not shown), the description covers the basic action. However, the omission of the agent_id parameter and lack of details on success/error behavior reduce completeness.

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 description documents the 'path' parameter with type and example, but completely omits the 'agent_id' parameter, which is required by the schema. With 0% schema coverage, the description fails to compensate for undocumented parameters.

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's purpose: 'Remove a file or folder on the agent.' The verb 'Remove' and resource 'file or folder' are specific, and it distinguishes from sibling tools like copy_file or move_file.

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 such as move_file or list_directory. The description only provides syntax, not context for selection.

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