Delete Nextcloud file

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

Annotations already declare destructiveHint=true and idempotentHint=true, which covers mutability. The description adds a behavioral caveat: 'Deleting the configured root itself is always refused.' This is useful context not present in annotations. However, it does not disclose whether folder deletion is recursive or if there are other side effects.

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. It front-loads the primary action in the first sentence and adds a critical safety note in the second. No unnecessary words or fluff; every word earns its place.

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 tool is simple (one parameter, no nested objects, output schema exists). The description covers the core action and the root-refusal safeguard. It does not mention recursive deletion for folders or error behavior, but these are likely captured by the output schema. Overall, it is adequate for a simple delete operation.

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 has a single 'path' parameter with 0% description coverage. The tool description does not explain what 'path' means, its format, relative vs absolute, or any constraints. The description fails to compensate for the lack of schema documentation, leaving the agent to infer path semantics from the parameter name alone.

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 action: 'Delete one file or folder.' It uses a specific verb and resource, and adds a safety note about refusing to delete the configured root. This distinguishes it from sibling tools like move_file or create_folder.

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 does not explicitly state when to use this tool versus alternatives. Usage is implied from the purpose (deleting files/folders), but no guidance is given on when deletion is appropriate versus moving or trash, or when not to use it. No alternatives are mentioned.

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