delete_system_backups

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

Annotations already provide destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the bar is lower. The description adds that the deleted item is a backup file and exposes the DELETE endpoint, but it does not add deeper behavioral context such as irreversibility, required permissions, or side effects. It does not contradict the annotations.

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 short and front-loaded: the core action appears in the first sentence, followed by the endpoint and the required argument. There is no filler, though the phrasing 'Backups to delete filename' is slightly clunky and could be clearer.

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 single-parameter destructive operation with annotations and an output schema, the description provides enough information: the action, the resource, the endpoint, and the required filename. It omits expected-error behavior or result details, but those are not critical given the output schema and simple tool contract.

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 provides the parameter name 'filename' and type 'string' with 0% description coverage. The description's Args block, though awkwardly phrased, does communicate that filename is the backup file to delete. This adds minimal but useful meaning beyond the bare schema.

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 opens with 'Delete a backup file,' a specific verb plus resource, and reinforces it with the DELETE /api/system/backups endpoint. This clearly distinguishes the operation from sibling tools like list_system_backups, create_system_backups, and patch_system_backups by action and target resource.

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?

There is no guidance about when to use this tool versus alternatives such as list_system_backups or patch_system_backups. The description also provides no exclusions, prerequisites, or caution about destructive consequences, leaving usage decisions entirely to inference.

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