Export Drawing To Svg

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that a drawing is rendered to SVG, but it does not explain whether the tool writes to output_path, returns SVG content, or has side effects. The behavior around output_path defaulting to null is left entirely to inference.

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 a single sentence with no filler, and it front-loads the core action and output format. It is appropriately concise, though that brevity comes at the cost of behavioral and parameter detail.

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?

An output schema exists, so return-value documentation is not strictly needed, but the description remains incomplete for a five-parameter tool with no annotations. It does not explain parameter semantics, output behavior, or when to choose this sibling over PDF/PNG exports.

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%, and the description does not compensate by explaining any of the five parameters. While parameter names like bg_color and dark_mode are suggestive, nothing clarifies semantic details such as how layout_name selects a layout or what happens when output_path is null.

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 an action: render a DXF CAD drawing to SVG format. It adds the vector and browser-viewing context, which helps distinguish it from raster exports like export_drawing_to_png. However, it does not explicitly contrast with export_drawing_to_pdf, which is also a vector-format sibling.

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 provides no explicit guidance on when to use SVG versus PDF or PNG exports. 'Crisp browser viewing' hints at a use case, but there is no mention of alternatives, exclusions, or conditions favoring this tool.

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