Create system backup

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

No annotations are provided, so the description carries the full burden. It only states that a backup is created, with no mention of potential side effects, required backup target configuration, or that a system backup is a Longhorn CRD operation. The docs link is helpful but the description itself lacks behavioral transparency.

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?

Single sentence with a supporting link, no redundant phrase. The core action is front-loaded and the docs link is placed after, keeping the description efficient.

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 is simple with one parameter, but with no annotations, no output schema, and no behavioral context the description is under-specified. It omits prerequisites (e.g., backup target) and expected outcomes, so an agent may call it without understanding side effects. The docs link helps but is not inline guidance.

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 explain the 'name' parameter at all. An agent must infer that 'name' is the backup name from the tool name, which is not reliable. With no param details in either schema or description, the agent cannot validate input semantics.

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 the specific action 'Create' and the resource 'Longhorn system backup,' clearly distinguishing it from sibling tools like systembackup_list/get/delete and systemrestore_create. The docs link adds authoritative context. No ambiguity about the tool's primary function.

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 gives no guidance on when to choose this tool over alternatives such as volume_snapshot_backup, volume_backup, or systemrestore_create. No prerequisites or context are mentioned, leaving the agent to infer the appropriate use case from the name alone.

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