Set plot3d outputs

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety/mutation profile is covered structurally. The description adds only the 5-quantity cap; it does not say whether existing outputs are replaced or appended, which is the key behavioral question for this tool.

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?

Two short sentences, front-loaded with the core action and the key constraint. The appended '[bulc-mcp rules] ASET-004, EVAC-008, OUT-003' block is cryptic pointer noise but does not bloat the text significantly.

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 2-parameter mutation tool with no output schema, the definition covers what to supply but omits replace-vs-append semantics and any indication of the resulting state. Annotations cover the safety profile and the schema covers parameter shape, so the gap is moderate rather than critical.

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 description coverage is 100%, so both arrays are documented ('Species IDs for VOLUME FRACTION quantities', 'e.g. ["TEMPERATURE","U-VELOCITY",...]'). The description's only added meaning is the maximum of 5 quantities; otherwise it defers to the schema, which is the expected baseline.

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?

States a specific verb+resource ('Set the Plot3D output quantities and species IDs') and anchors it to a known dialog context ('NUM dialog'). No sibling tool covers Plot3D output selection, so the purpose is distinguishable, though it doesn't explicitly contrast with adjacent output tools like update_dump_config or set_numerics.

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 only actionable guidance is the 'up to 5 quantities' limit. There is no statement of when to use this versus other output/config tools, no prerequisites, and no exclusions. The bulc rule IDs hint that constraints exist but never say what they are.

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