list_system_backup

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds no behavioral context beyond repeating that this is a read. It does not mention what the response contains, pagination, authorization needs, or any other runtime behavior. No contradiction exists, but the description carries almost no additional transparency burden.

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 very short and front-loads the action, with the endpoint adding a concrete reference. For a zero-parameter read operation, this level of brevity is not wasteful, though it leans toward under-specification rather than effective conciseness.

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 zero parameters, a read-only annotation set, and an output schema, an agent can likely invoke the tool correctly. However, the description still leaves the tool's exact purpose ambiguous—'Read Backup' could mean reading a single backup versus listing all backups—and offers no usage context, so it is only minimally adequate.

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 schema description coverage is effectively 100%, so there is no parameter semantics burden on the description. The baseline of 4 applies because nothing needs to be explained beyond what the empty schema already communicates.

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 says 'Read Backup' and provides the GET endpoint, so it does state a verb and resource. However, 'Read Backup' is a vague paraphrase of the tool name and does not clarify that this lists system backups or distinguish it from related backup operations. It is not a pure tautology, but it lacks the specificity needed for strong differentiation.

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 on when to use this tool instead of alternatives such as create_system_backup_restore_by_id, delete_system_backup_by_id, or list_system_status. The description gives no context about use cases, exclusions, or related tools.

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