arcane_get_volume_sizes

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

No annotations are provided, so the description must carry the disclosure burden. The verb 'Get' implies a read-only operation, but the description discloses no other behavioral traits such as return format, error handling, or prerequisites. It adds little beyond what the tool name already conveys.

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, front-loaded sentence with no filler. It efficiently communicates the tool's purpose without unnecessary detail.

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 read operation, the description covers the core functionality. While there is no output schema, the phrasing 'disk sizes for all volumes' adequately implies the return value. More detail on the exact response structure would improve completeness, but the tool's low complexity makes this adequate.

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 fully documents the only parameter (environmentId) with a clear description. The tool description references the environment scope but does not add additional semantics beyond what the schema provides, so the baseline score of 3 applies.

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 uses a specific verb ('Get') and resource ('disk sizes for all volumes') with a clear scope ('in an environment'). It distinguishes itself from siblings like arcane_list_volumes or arcane_get_volume by focusing specifically on disk sizes rather than general volume information.

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 states what the tool does, but it does not explicitly mention when to use it over alternatives or any exclusions. The intended usage is implied by the tool's specific function, but no direct guidance is provided compared to sibling tools.

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