panelica_backups_get_v1_backups

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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by specifying required scope backups:read, the HTTP method, and the exact data scope (full and incremental backups), giving auth and content context beyond the structured annotations. No contradiction.

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 purpose is front-loaded in the first sentence, followed by three compact metadata lines. No filler or redundant restatement; it is minimal without losing necessary context.

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 zero-parameter read-only list endpoint, the description is complete: it states HTTP method, category, required scopes, safety, and what is returned. No output schema is present, but the return description and tool title sufficiently convey the result for an agent to invoke it correctly.

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, so there is nothing for the description to explain. The schema description coverage is trivially complete, and the baseline for a no-parameter tool 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 opens with 'Returns all full and incremental server backups,' naming a specific verb, a resource, and a scope. This clearly distinguishes the list-all endpoint from sibling operations that target a filename or create backups. The accompanying title reinforces the purpose.

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 gives clear operational context—HTTP GET, Category: Backups, required scope backups:read, read-only—so an agent can tell this is a safe list operation. However, it does not explicitly say when to prefer this endpoint over the sibling panelica_backups_get_v1_backups_filename or panelica_backups_post_v1_backups, so usage guidance is implied rather than explicit.

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