bricks_create_full_backup

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

With no annotations provided, the description carries full burden. It discloses that the backup excludes media files and database, and advises pairing with a host snapshot. This adds important behavioral context, though it does not specify whether it overwrites previous backups or the exact effect on the server.

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 two sentences, highly concise, and front-loaded with the core action. Every sentence adds value: the first defines the operation, the second provides usage guidance and limitations. No wasted words.

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?

The description covers purpose, usage, and limitations, but lacks information about the return value (e.g., file path or success status) and technical details like file naming or location. Given no output schema, this information would be helpful for an agent to confirm completion.

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 with 100% schema description coverage. The description does not need to add parameter details since none exist; the baseline of 4 is appropriate as the description focuses on the tool's action rather than parameter meaning.

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 explicitly states the tool creates a full-state backup of the Bricks layer including all pages, drafts, templates, global styles, etc., as a single JSON file. It also clarifies what is not backed up (media, database), clearly distinguishing it from other backup-related sibling tools.

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 recommends using the tool before risky bulk operations and suggests pairing with a host snapshot for full disaster recovery. This provides clear usage context, though it does not explicitly mention when not to use it or list alternative tools for lighter backups.

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