bricks_restore_backup

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

The description does not disclose that restoring overwrites current data, whether a backup is created automatically, or any permission requirements. With no annotations, this lack of detail is a significant gap for a destructive operation.

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?

Single sentence, no extraneous text. Concise but could be more informative without becoming verbose.

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 restoration tool with no output schema and no annotations, the description should explain the restore process (e.g., overwrites current data, may create backup, irreversible). It omits these critical details, leaving the agent underinformed.

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?

Input schema provides 100% coverage with descriptions for both parameters (slot and page_id). The description adds no additional semantic context beyond what the schema already offers.

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?

Description clearly states the action (restore) and target (page's Bricks data from a backup slot). It differentiates from full-site restore and snapshot restore by specifying 'page's Bricks data' and 'backup slot'. However, it does not explicitly contrast with sibling tools like bricks_restore_full_backup or bricks_restore_snapshot.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no mention of when not to use it. The agent is left to infer context from the name and description alone.

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