Get backup backing image

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'Get' and 'by name' convey a read/retrieval operation with no side effects, which is sufficient for a simple getter, but it does not state return shape or failure behavior. Minimal but not misleading.

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?

One sentence and a link, with the operative verb and resource front-loaded and no filler. Every element earns its place.

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 simple one-parameter getter with no output schema and no annotations, the description is nearly complete: it names the resource, the operation, and the identifying parameter. It only lacks explicit guidance on when to choose this over list/search siblings.

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 input schema provides only a `name` string with 0% description coverage. The description adds that the parameter is used to select a single backup backing image, which is helpful but largely restates the parameter name. It does not describe format, uniqueness, or how to discover valid names; the docs link is the only additional resource.

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 verb-resource pair ('Get a single backup backing image') and the selection mechanism ('by name'), which clearly distinguishes it from list-oriented siblings like backupbackingimage_list and mutation tools like backupbackingimage_delete. It is unambiguous about what the tool does.

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 when to use it—when a caller already has a specific name—but it never explicitly contrasts it with alternatives (e.g., backupbackingimage_list) or states when not to use it. The Longhorn docs link provides background but not decision guidance.

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