Render Preview Set

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

No annotations exist, so the description carries the full disclosure burden. It does add genuine behavioral facts: parallel execution, preserved ordering, and a six-default-view behavior when views is null, plus a 1–12 cardinality limit. However, it leaves key behaviors unexplained, including the semantic difference between render_mode 'preview' and 'render', the meaning of a 'custom' view, and how version affects the output.

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 single 14-word sentence front-loads the verb and the central default-vs-requested distinction, then compresses two behavioral traits ('in parallel', 'preserving order') without waste. Every word earns its place.

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 six parameters, zero annotations, and 0% schema coverage, this description is too thin for reliable invocation. An agent cannot determine which views constitute the six defaults, what 'custom' names refer to, or what render_mode 'render' changes relative to 'preview'. The presence of an output schema mitigates the return-value gap, but not these parameter-level and mode-level holes.

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, but it only partially explains the views parameter (null → six defaults, provided → 1–12 named views). Width, height, version, render_mode, and project_id receive no semantic explanation in either the schema or the description, leaving an agent to guess at their roles.

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 names a specific verb ('Render') and resource (project views) with a precise scope: six default views or 1–12 named views, executed in parallel with order preserved. This is clear and specific, but it never distinguishes itself from the near-twin sibling render_preview, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus alternatives. With the sibling render_preview almost certainly covering the single-view case, the description offers no condition or cue that would route an agent to one tool over the other.

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