qui_backups

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals HTTP methods and endpoints, which imply destructive operations like `qui_delete_all_backup_runs`, but it does not warn about irreversible deletion, permissions, side effects, rate limits, or response behavior.

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 compact and scannable: one short instruction paragraph followed by a bullet list of ten operations with method and path. The opening sentence is slightly redundant with the tool name, but every other line contributes necessary endpoint mapping information.

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?

Given the high complexity of ten distinct operations and the generic `arguments` schema, the description provides a useful operation-to-endpoint map and general argument conventions. However, it lacks operation-specific parameters such as required query strings or request body schemas, leaving some invocations under-specified. The existence of an output schema reduces the need to document return values, but does not fill this gap.

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 input schema only has an enum and a generic `arguments` object with 0% description coverage, so the description must compensate. It does so by explaining the argument envelope—path variables in `arguments`, query values in `arguments.params`, and body in `arguments.body`—and mapping each operation to its endpoint path with visible path parameters. It still omits per-operation query and body field details, but the provided structure is significantly useful.

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 enumerates ten backup-related operations with their exact HTTP methods and paths, making it clear this tool exposes qui backup REST endpoints. It distinguishes from sibling tools by the backup domain and consistent qui_ prefix, though the opening phrase 'qui backups operations on qui' is somewhat tautological.

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 implies usage context by listing all backup operations and explaining how to invoke them with `operation` and `arguments`. It does not provide explicit guidance on when to prefer this tool over sibling qui_* tools or mention exclusions, so the guidance is implied rather than stated.

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