profilarr_delete_backup

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

While the annotation 'destructiveHint: true' covers the destructive nature, the description adds little beyond that, only restating the location 'from the server.' It does not disclose whether deletion is permanent, reversible, or requires special permissions, leaving the agent without extra behavioral context.

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 with no filler, front-loaded with the imperative verb 'Delete.' It is appropriately sized for a simple operation and maintains high readability.

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 is sufficient for a basic delete operation, but it lacks context on how to obtain valid filenames (e.g., from list_backups) or any prerequisites. The presence of an output schema mitigates the need to explain return values, but the missing usage context makes it only minimally complete.

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 does not mention the 'filename' parameter or explain how to specify which backup to delete. With schema description coverage at 0%, the agent has no additional guidance beyond the parameter name and type, which is insufficient for understanding what values are expected.

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 action 'Delete a backup archive' with a specific verb and resource, distinguishing it from sibling backup operations like create, download, or list backups. It leaves no ambiguity about what the tool does.

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 provides no guidance on when to use this tool versus alternatives, such as listing backups first or confirming the backup is no longer needed. It simply states the action without any contextual cues about appropriate usage.

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