batch_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the comma-separated input format but does not disclose whether deletion is permanent, recursive, or what happens if a path does not exist. For a destructive tool, this lack of warning is a significant gap.

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 a single sentence, front-loaded with the action and object, and includes the essential input format in a concise parenthetical. Every word contributes to understanding the tool's purpose and parameter format, with zero 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?

The description covers purpose and parameter format, and an output schema exists so return values need not be explained. However, for a destructive tool with no annotations, it lacks behavioral context such as irreversibility or error behavior. The low parameter count and simple structure mitigate the incompleteness, but additional safety notes would improve it.

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 schema only defines 'paths' as a string, with no description. The tool description compensates by explaining that paths are comma-separated and can refer to files or directories. This adds crucial meaning beyond the schema, though it does not provide details like path format or relative/absolute resolution.

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 function: batch deleting files/directories in Nutstore. The verb 'delete' and resource 'files/directories' are specific, and the phrase 'batch' distinguishes it from the sibling tool 'delete_file'. The parenthetical about comma-separated paths adds further clarity.

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 batch aspect of the tool implies its use case: when multiple paths need to be deleted at once. However, the description does not explicitly state when to use this tool versus alternatives like 'delete_file', nor does it mention any prerequisites or constraints. Guidance is implied but not fully articulated.

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