supervisor_restore_backup

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

The description provides minimal behavioral traits: it labels the operation as 'DANGEROUS' and requires confirmation. However, no annotations are present, so the description should disclose more details about side effects, authorization requirements, or operational impact. It falls short.

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-loaded with the action, but it could be slightly more informative without becoming verbose. The single sentence conveys the core purpose but omits useful details.

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 complexity of a dangerous restore operation, the description lacks context about prerequisites, effects, return values (though output schema exists), and error conditions. It is not sufficiently complete for safe agent usage.

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 3 parameters (slug, password, confirm) with 0% description coverage. The description only mentions 'confirm' requirement, but does not explain the slug or password parameters, leaving the agent without essential context to use them correctly.

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 clearly states the action 'Restore a full backup by slug', which is a specific verb and resource. It distinguishes from sibling tools like supervisor_create_backup and supervisor_delete_backup.

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?

No explicit guidance on when to use this tool versus alternatives. It only mentions a precondition ('requires confirm=True'), but does not indicate when restore is appropriate compared to other operations.

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