render_svg

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fully discloses that the tool is not implemented, that it will always return a failure object with 'success': False, and specifies the error_type and suggestions fields. This is complete transparency for a stub tool, leaving no ambiguity about its runtime behavior.

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 contains unnecessary implementation details about 'Day 2 work', 'bassimeledath's warm-Chromium approach', and 'locally vendored excalidraw JS bundle' that do not help an agent select or invoke the tool. The return format is clearly structured, but the clutter makes it less concise than it should be.

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 two-parameter tool with an output schema (return format), the description adequately covers the essential context: the not-implemented status, the underlying technology, and the exact failure return format. The main gap is the absence of any note about what the tool would do if it were implemented, but since it is a stub, the current information is 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?

The schema already provides descriptions for both required parameters (elements_json and output_path) with 100% coverage. The tool description adds no additional meaning or nuance beyond what the schema states, so the baseline score of 3 is appropriate.

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 'Render Excalidraw element JSON to SVG via headless Chromium (Playwright)', providing a specific verb, resource, and method. This distinguishes it from sibling render tools like batch_render by indicating it handles a single conversion, and the 'NOT IMPLEMENTED YET' status clarifies its current non-functional state without obscuring the intended purpose.

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 'NOT IMPLEMENTED YET' warning implicitly signals the agent not to use this tool until it is ready, which is a form of usage guidance. However, it does not explicitly state when it should be used, nor does it point to alternatives such as batch_render for current rendering needs, leaving the when-to-use guidance incomplete.

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