backups_admin_list

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

No annotations are provided, so the description carries the burden. The verb 'List' conveys a read-only operation with no mutation, and 'admin-level' hints at required privileges. It does not disclose additional behavioral details such as sensitivity of settings or whether the call is safe to run repeatedly, but for a no-parameter list tool this is a minor gap.

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 entire description is a single compact phrase with no filler or redundant wording. The action ('List') and scope ('admin-level backups / backup settings') are front-loaded and immediately usable.

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 simple no-parameter list operation with an output schema, the description is nearly sufficient. The only weakness is the slight ambiguity of 'backups / backup settings' (whether one or both are returned), and no explicit routing versus sibling backup tools.

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 tool has zero parameters and the input schema is empty, so schema coverage is complete at 100%. The description adds no parameter semantics, but none are needed; the baseline for zero-parameter tools applies.

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 states a specific verb ('List') and resource ('admin-level backups / backup settings'), making the core purpose clear. It is distinguishable from sibling tools like backups_create, backups_restore, and backups_admin_now by the listing action and admin scope, though it does not explicitly contrast itself with them.

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?

Usage context is implied by 'admin-level' and 'List': an agent can infer it is for inspecting admin-level backup data rather than creating or restoring backups. However, there is no explicit when-to-use guidance, exclusions, or pointer to alternative tools.

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