bookshelf_restore_backup_upload

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

The description adds 'WRITE: this modifies your Bookshelf instance,' which is redundant with readOnlyHint=false. It does not disclose what files are uploaded, whether existing data is replaced/destroyed, or any confirmation/cancellation behavior. Given the tool name suggests a restore operation, the lack of detail about potential data loss is a significant transparency gap.

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, but it is not concise in a useful way—it is unclear and poorly phrased. 'Create system backup restore upload' is not an idiomatic English phrase, and the sentence structure obscures the action. The warning is clear but the main purpose is mangled.

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 tool has no parameters and an output schema is present, but the description fails to explain the tool's behavior. It does not clarify what input is expected (e.g., file upload), how the restore process works, or what the output represents. This is particularly problematic given the name suggests a complex backup/restore operation that could have significant side effects.

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?

There are zero parameters in the input schema, so the description has no parameter documentation burden. The schema is trivially 100% covered. A baseline of 4 is appropriate because the description cannot add meaning beyond the empty schema, but there is also nothing omitted.

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 upload' is a confusing, ungrammatical phrase with no clear verb-object relationship. It does not clearly state whether the tool uploads a backup, restores one, or creates a restore point. It vaguely suggests an upload/restore action but is not specific enough to distinguish from the sibling 'bookshelf_restore_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?

The description provides no guidance on when to use this tool versus alternatives like 'bookshelf_restore_backup'. It does not mention prerequisites, file requirements, or scenarios where this tool is preferred. The only extra information is the WRITE warning, which is not usage guidance.

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