render_view

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

With no annotations, the description carries the full burden and does well: it discloses the PNG side effect, the non-obvious state mutation ('Arguments given here also update the session's default view'), and a hard prerequisite constraint ('Targets must come from query_region on the rendered cell'). It stops short of discussing cost, latency, or failure modes, but the non-obvious behaviors are surfaced.

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 the action and return value in sentence one, followed by the state-effect caveat, then a clean per-argument list. Every line earns its place; nothing is repeated from the schema.

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 7-parameter rendering tool with an output schema, the description covers all parameters, the state side effect, the annotation prerequisite, and return semantics. An agent has everything needed to invoke it correctly.

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 0%, so the description must compensate fully, and it does: every one of the 7 parameters is documented with format, defaults, and provenance (session_id from `open_layout`, layers as `[{"layer": int, "datatype": int}]`, image_size default 1200x800, style enum values). This adds substantial meaning 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 first sentence gives a specific verb ('Render'), resource ('layout geometry'), output ('to a PNG') and return value ('absolute path'). It also positions itself relative to the sibling `set_view` by noting the shared session-state effect, so an agent can distinguish it from that tool without opening the schema.

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?

Usage is implied by the rendering workflow (open_layout -> query_region -> render_view) and by the reference to `set_view`, but there is no explicit when-to-use / when-not-to-use statement or named alternative. The agent must infer that this is the visual-output step.

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