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

Annotations already cover the safety profile (readOnlyHint true, destructive false, closed world), so the bar is lower; the description still adds real value by disclosing render semantics — facing layer at full strength with others faded — and the return payload (px_per_mm and region echoed, plus a downloadable workspace.render.png). It omits the async/job-follow-up behavior, which is only carried by the wait_s schema field.

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?

A dense but efficient paragraph that front-loads what the image contains before enumerating options and the return payload. Nearly every clause conveys distinct information, with only minor cramming of option descriptions into one sentence.

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?

With no output schema, the description correctly explains what comes back (scale, region, PNG download location) so a follow-up crop is exact. Combined with schema-level wait_s text about the running-job path, an agent has enough to call it, though the unexplained markers and max_width params leave small 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?

Schema description coverage is only 21% across 14 params, and the description meaningfully compensates by naming and explaining side, region, drc_markers, ratsnest, highlight_nets/highlight_refs, layers, refs and courtyards. However, markers (custom annotations with labels) and max_width are never explained, and refs/courtyards are only implied by a list of drawing elements rather than described as toggles.

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: an 'exact 2D picture of the board' with an enumerated layer set (copper, pads, vias, pours, outline, courtyards, refs). That makes it clearly distinct from data-oriented siblings like board_census or get_board_context, though it never names a sibling to differentiate against.

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 through the option clauses ('drc_markers to circle every DRC violation', 'ratsnest to draw the open connections', 'region ... for a crop'), but there is no explicit statement of when to render versus using other board-inspection tools, nor any exclusion.

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