set_display

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

With no annotations, the description clarifies that min/max 'does not alter the data,' indicating non-destructive behavior. It doesn't detail other traits like permission needs or reversibility, but the behavior is straightforward.

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 concise at 7 lines with a clear Args structure. Every sentence provides essential information without redundancy.

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 description covers purpose, parameters, and non-destructive nature. It lacks detail about return values or confirmation of changes, but given the simple display operation, it is mostly complete.

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 coverage is 0%, so the description fully compensates by explaining each parameter: colormap examples, min/max meaning, opacity range, and volume default. This adds significant value beyond the bare schema.

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 tool 'set colormap, intensity window and opacity for one layer,' specifying the verb and resource. It uniquely handles display settings, distinguishing from siblings like load_volume or navigate.

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 mentions 'Defaults to the most recently loaded' volume, implying typical use. However, it does not explicitly state when not to use or provide alternatives, though the context is clear.

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