Create backup target

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'Create a new backup target' and points to Longhorn docs; it does not disclose potential failure modes, whether creation is idempotent, whether credentials or external connectivity are required, or what side effects may occur during creation.

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 a single focused sentence followed by a reference link. It is front-loaded with the core purpose and contains no filler or redundant restating of the schema.

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 annotations, no output schema, and a nested `extra` parameter. The description is too thin to fully prepare an agent: it does not explain expected input requirements, return behavior, or operational constraints. The Longhorn docs link provides a reference but does not substitute for inline tool 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?

The description adds no parameter-level meaning, but the input schema already documents `extra` as 'Additional Longhorn fields, merged verbatim into the request body.' The `name` field is self-evident from its name and role. At 50% schema coverage, this is acceptable, though the description could have clarified required name 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?

The description states a specific action and resource: 'Create a new backup target.' The verb 'create' plus the resource 'backup target' clearly distinguishes this tool from the sibling backuptarget_update, backuptarget_delete, and backuptarget_sync operations without confusion.

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?

Usage is implied: this tool is for creating a backup target, while siblings are for updating, deleting, or syncing. However, the description gives no explicit when-to-use guidance, prerequisites, or exclusions, so the agent must infer the appropriate context from the operation name.

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