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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating that the call asks no human and by summarizing the returned state (writable copy, mirror/last sync, recent run outcomes).

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 definition is short and front-loads the returned-state summary before the no-human note. Both sentences carry useful information, though the phrasing is slightly indirect and does not explicitly name the tool's action.

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?

With no output schema, the description partially compensates by naming the kinds of state returned. However, it leaves parameter scoping and result structure underspecified, which matters for an inspection tool with three optional filter parameters.

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?

Only the volume parameter has any schema description ('Omit for every Volume here'), while project and environment are undocumented at 33% coverage. The description does not compensate by explaining what those parameters filter or how optional scoping works.

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 identifies this as a volume inspection tool that reports where a volume's data lives, including writable copy, mirror/last sync, and recent run outcomes. It is distinguishable from mutation-oriented siblings like volume_mirror or volume_update, though it never explicitly states 'show/inspect a Volume' as the verb.

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?

There is no explicit guidance on when to use this tool, when to prefer alternatives, or what the optional volume/project/environment scoping means. Usage is only implied by the name volume_show and the description of returned data.

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