Sync backup target

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

With no annotations present, the description carries the full behavioral disclosure burden. It does indicate a 'Force' resync operation, which hints at non-idempotent or state-changing behavior, but it does not state side effects, permissions required, reversibility, or whether existing backup state is replaced or merged.

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 appropriately terse and front-loaded with the action, followed by a documentation link. It contains no filler or redundant phrasing, though its brevity does sacrifice explanatory richness.

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?

For a tool with five undocumented parameters, no annotations, no output schema, and many related siblings, this description is far from complete. An agent cannot determine how to set the boolean flags, what values name expects, or when this tool is the right choice over backupvolume_sync.

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 any of the five parameters. The boolean flags syncBackupTarget, syncBackupVolume, syncAllBackupTargets, and syncAllBackupVolumes, as well as the required name field, are left completely ambiguous, so the description adds no semantic value beyond the raw schema.

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 clearly states a specific action ('Force Longhorn to resync') and the resource ('backup target/backup volume state'), so the core purpose is identifiable. It loses the top score because sibling tools like backupvolume_sync exist and the description does not explicitly distinguish the two.

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 essentially no guidance on when to invoke this tool versus alternatives such as backupvolume_sync or backuptarget_update. The word 'Force' implies a troubleshooting or resync scenario, but there are no explicit conditions, prerequisites, or exclusion notes.

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