overlay

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

Discloses key behavioral traits: display-only, no registration, alignment requirement. No annotation provided so description carries burden, and it does well.

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?

Front-loaded with core action, followed by essential warnings and parameter list. Every sentence serves a purpose; mild repetitiveness in param docs.

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?

Covers operation, return value, behavioral boundaries, and parameter details. Lacks mention of error handling or result format, but adequate for visualization tool.

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?

With 0% schema coverage, description compensates by explaining each parameter's role, defaults, and constraints (e.g., opacity range). Adds clarity beyond schema types.

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 the verb 'stack' and resource 'loaded volumes', and distinguishes from siblings like compare_volumes by emphasizing display-only and no registration.

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?

Provides guidance on when not to use (if volumes unaligned) and explains defaults, but could be more explicit about alternatives.

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