render_preview_svg

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

No annotations are provided, so the description must carry the full burden. It states the output is a wireframe SVG in millimeters but omits whether the tool returns SVG content, writes a file, or what permissions are needed. For a rendering tool with no structured safety or behavior hints, this is a significant gap.

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?

Two sentences, front-loaded with the core purpose and then the only parameter's effect. Every sentence earns its place with no redundancy or filler.

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 tool is simple (one optional parameter), but the absence of an output schema and any description of return values, side effects, or file output leaves the agent without essential information to invoke it confidently. The description is too thin for a rendering tool with no structured behavioral metadata.

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% for the single parameter. The description compensates partially by explaining that entity_ids is optional and limits which shapes are drawn, adding meaning beyond the bare array type. However, it does not clarify the expected ID format or the default behavior when omitted.

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 states a specific verb ('render'), output format ('SVG'), visual style ('wireframe'), and subject ('entities') with units ('mm'). It does not distinguish this tool from sibling tools like render_preview or generate_svg, leaving ambiguity about when to choose it over those alternatives.

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 only usage guidance is that entity_ids is optional and limits which shapes are drawn. There is no indication of when to use this tool versus render_preview, generate_svg, or batch_generate_svg, nor any prerequisites or context.

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