create_backup

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

Annotations include readOnlyHint=false, so the write nature is already known. The description adds the access requirement ('Requires backup access') but fails to disclose other traits such as side effects, storage behavior, or return value. Given the annotations already indicate a non-read-only operation, the added context is minimal.

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 concise, substantive, and front-loaded. It consists of two short sentences with no filler, making it easy to parse and act on.

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?

With no output schema and minimal annotations, the description carries the burden of explaining the tool. It omits parameter semantics, result format, and any operational nuances, making it incomplete for a 2-parameter creation tool. The existence of sibling tools also highlights the need for clearer scoping.

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 description coverage is 0%, and the description does not mention either parameter (name or server_id). The agent is left without any guidance on what 'name' should be or how 'server_id' affects the backup, making the description entirely unhelpful for parameter use.

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 a server backup' clearly states the action and resource, and the verb 'create' distinguishes it from sibling backup tools like list_backups, delete_backup, and deploy_backup. However, it does not explicitly name alternatives or scope details, so it falls short of a perfect 5.

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 implies usage when a backup needs to be created and notes the prerequisite 'Requires backup access.' It does not explicitly state when to use this tool versus alternatives (e.g., deploy_backup, delete_backup), nor does it mention any exclusions or conditions.

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