load_volume

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

Discloses return values (shape, voxel size, etc.) and states no preprocessing is performed. Lacks mention of side effects on session state, but adequately covers safety for a load operation.

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?

Concise paragraph covering purpose and return info, followed by clear argument descriptions. Every sentence is informative and efficient.

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 3-parameter tool with no output schema, the description fully covers inputs, expected outputs, and key behaviors (no preprocessing, space assertion). No obvious gaps.

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?

Despite 0% schema coverage, description thoroughly explains each parameter: path format, name default, and space assertion semantics. Adds significant value 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?

Clearly states it loads a preprocessed NIfTI volume (MRI, PET) and returns detailed info. Distinguishes from sibling 'load_atlas' which loads atlases.

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?

Specifies that the volume must be already-preprocessed, but does not provide explicit guidance on when to use versus alternatives like compare_volumes or roi_stats.

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