list_system_backup

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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate those. However, it adds no behavioral detail beyond the HTTP method, such as what the response contains or whether backups are returned in any particular order. No contradiction exists, so a mid-range score is appropriate.

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 extremely compact: a one-line purpose statement followed by the endpoint. There is no wasted prose, and it is easily scannable for an agent.

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 that this is a simple, zero-parameter, read-only endpoint with a rich output schema and strong annotations, the description is nearly sufficient. It would benefit from one sentence clarifying that it retrieves the list of system backups, but the endpoint and annotations fill most of the 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 has zero parameters and schema description coverage is 100%, so there are no parameter semantics to convey. Per the baseline for zero-parameter tools, the description is not expected to add parameter-level detail.

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 clear verb and resource: 'Read Backup.' The included endpoint 'GET /api/v3/system/backup' reinforces the system backup context and distinguishes it from other list_system_* tools. It is somewhat terse and largely echoes the tool name, but it is unambiguous.

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 call this tool versus alternatives such as list_system_status, list_system_task, or delete_system_backup_by_id. There is no contextual hint about backups being read-only or when a user would need this endpoint.

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