Render View

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds behavioral context by explaining the deflection parameter (tessellation accuracy, smaller = finer mesh, slower) and the return format (png_base64, width, height, view, vertices, triangles). This goes beyond the annotations and helps the agent understand performance trade-offs and output structure.

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 compact and front-loaded with the core purpose. It uses a bullet-like list for parameters and a clear return format line. Every sentence adds value, with no filler or repetition of schema fields.

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 is complete for a read-only rendering tool: it covers the output format, key parameters, and performance trade-offs. It lacks explicit mention of the 'handle' parameter's meaning, but the schema marks it as required and the context of a shaped object makes it inferable. No output schema exists, so the return format description is valuable and sufficient.

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. It explains the 'view' parameter with all allowed values, 'deflection' with its meaning and trade-off, and 'edges' with its effect. However, it does not explain 'width', 'height', or 'handle' beyond what the schema provides, which is a minor gap given the schema already has defaults and titles.

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 renders an isometric/orthographic view of a shaped object as a PNG, with a specific verb ('render'), resource ('shaped object'), and output format. It distinguishes itself from sibling render tools like render_photoreal and render_fem_results by specifying the view types and PNG output.

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 implies usage by listing view options and parameters, but does not explicitly state when to use this tool versus alternatives like render_photoreal or render_fem_results. The context is clear for a rendering tool, but no explicit exclusions or alternative routing is provided.

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