bookshelf_restore_backup

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

The WRITE note and 'modifies your Bookshelf instance' add only redundant context since annotations already indicate readOnlyHint=false. The description does not disclose whether the restore overwrites existing data, requires downtime, or has irreversible effects, which is critical for a restore 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?

The description is very brief, but the purpose sentence is ambiguous and the structure is minimal. The WRITE warning is a useful addition, yet the overall text is under-specified rather than effectively concise.

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 tool's complexity as a restore operation and the presence of an output schema, the description still fails to explain what the id refers to, what the restoration entails, or any side effects. It is a bare minimum that leaves critical information gaps.

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 only parameter 'id' has no description in the schema, and the tool description does not mention it at all. With 0% schema description coverage, the description fails to clarify what the id refers to (presumably a backup id), leaving the agent unable to invoke the tool 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 'Create system backup restore' is awkward and vague. It does not clearly state that this tool restores a backup identified by an id, nor does it distinguish itself from sibling tools like restore_backup_upload. The name is clearer than the description, which adds little clarity.

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 versus alternatives such as bookshelf_restore_backup_upload or bookshelf_delete_system_backup. No prerequisites, context, or exclusions are provided, leaving the agent to guess the appropriate use case.

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