Create a backup

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

With no annotations, the description carries the full behavioral burden but only clarifies one parameter. It does not say whether the backup is synchronous or async, how long it takes, whether it is destructive to existing backups, or whether permissions are required — significant gaps for a mutation tool.

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?

Two short sentences, front-loaded with the core purpose, and the second sentence is targeted at the one parameter that genuinely needs clarification. No wasted text.

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?

An 8-parameter mutation tool with no annotations, no output schema, and half the schema descriptions missing. The description addresses only one parameter and none of the runtime behavior, so it is well short of what an agent needs to invoke this confidently.

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?

Schema coverage is 50%, and the description usefully explains the 'ignored' parameter's format (newline-separated glob patterns) where the schema provides no description at all. However, 7 other parameters — including required 'server', 'name', 'is_locked', and the inline credential overrides — get no mention in the description, so it only partially compensates.

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?

States a specific verb and resource ('Start a new backup'), which unambiguously separates it from backup_list, backup_restore, and backup_delete. It doesn't explicitly name a contrasting sibling, but the operation is self-evident from the phrasing.

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 versus alternatives, and no prerequisites such as whether the server must be online, whether it counts against a backup limit, or what happens if a backup is already running. Usage must be inferred entirely from the name.

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