render_preview

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered. The description adds only that the render targets the *current* drawing and yields a PNG, but says nothing about resolution, whether a file is written, or whether a viewer is opened — modest added value against an already-strong annotation set.

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 front-loaded sentence with no filler; the verb and output format appear immediately and every word carries information.

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 simple zero-parameter, non-destructive render tool with full annotation coverage, the description is sufficient: an agent knows it returns a PNG of the current drawing for visual verification. The only gap is the absence of an output schema combined with no statement of what the return payload actually looks like.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. Schema coverage is nominally 100% because the object is empty.

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 (Render) plus resource (the current drawing) and names the output artifact (PNG image). The purpose is unambiguous, though it never distinguishes itself from the sibling export_drawing, which an agent could reasonably confuse with a preview render.

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 clause 'so you can check the result visually' implies the usage context: call it to verify drawing state after mutating operations. However, it gives no explicit when-to-use trigger, no exclusions, and no mention of the alternative export_drawing for producing a file.

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