Get shard group

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

With no annotations, the description must carry the behavioral disclosure burden, but it only says 'Get' and provides a docs link. It does not state behavior for a missing/invalid id, whether the operation requires special privileges, or what response the caller can expect.

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 two short sentences and wastes no words. The core action is front-loaded, and the documentation link is useful and clearly separated.

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 a simple one-parameter getter, so the absence of an output schema is not on its own fatal, but the description leaves out how to obtain/format the id and what the return payload is. The linked Longhorn docs partially compensate for the missing context.

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%, so the description needs to explain the 'id' parameter beyond its name. Saying 'by id' only repeats the obvious and does not clarify id format, source, or whether the id is numeric/name-based. This is insufficient compensation for the missing schema documentation.

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 the exact operation ('Get'), the resource ('shard group'), and the selection criterion ('by id'), so an agent immediately knows what the tool does. 'A single' also differentiates it from shardgroup_list without needing to open schemas.

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 phrase 'by id' implies this is the single-item retrieval tool rather than shardgroup_list, but the description never explicitly says when to choose it over alternatives such as shard_get or shardgroup_list. There is no when-not-to-use guidance.

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