Delete Nextcloud file

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is known; the description adds the non-obvious boundary facts (single item per call, root refused, confined to the connected workspace). It does not say whether deletion is permanent or moves to a trash/versions store, which is the one behavioral gap that matters for a destructive tool.

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?

Two short sentences with zero waste; the primary scope constraint is front-loaded and the refusal rules follow as compact negative constraints. No restatement of the tool name or annotations.

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 one-parameter destructive tool with an output schema and full annotation coverage, the description covers enough to call it safely: scope, target confinement, and the root refusal. The remaining gaps (path format, permanence/trash behavior) are real but minor against the annotations and 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 description coverage is 0% for the single `path` parameter, so the description must carry the load. It indirectly scopes the path to the user's private workspace root, which usefully rules out absolute URLs or other mounts, but never states whether the path is relative or absolute, leading-slash conventions, or whether folders are accepted.

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?

States a specific verb ("Delete") and a tightly scoped resource ("one item only inside the user's connected private Nextcloud workspace root"). It is unmistakably the only destructive single-item removal tool among the siblings, though it never names an alternative (e.g. move_file) for non-destructive relocation.

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?

Gives concrete when-not conditions: deleting the root is refused, and other accounts/hosts/arbitrary URLs cannot be targeted. What's missing is positive routing guidance — nothing tells the agent to prefer move_file or a trash-based flow when the user may want to recover the item.

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