autocad_render_preview

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety profile is covered; the description adds genuinely new behavioral context beyond that — two distinct backends with different mechanisms, the matplotlib dependency requirement ('preview' extra), and the reason both can be non-idempotent. It does not address file overwrite behavior or whether a live AutoCAD connection is required for the COM path.

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?

Nicely front-loaded: purpose first, then backend behavior, then Args, then Returns. The Args/Returns sections duplicate what the schema and output schema already express, which is the only redundancy; the prose is otherwise tight and well-organized.

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 one-parameter render/export tool with annotations and an existing output schema, the description covers the essentials: what it produces, the two backends, the extra dependency, and the return payload (even though the output schema already defines it). Minor gaps remain around overwrite semantics and whether an open document is required, but nothing critical is missing for correct invocation.

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 Args block restates path/width/height, but the values it gives (example '.png', range 100-4000, default 1200x800) are already present in the schema's defaults, min/max, and descriptions. It therefore adds little meaning beyond the structured schema. Reported schema description coverage is 0% (measured at the top-level 'params'), so the description does at least surface the parameter contract, keeping this at a baseline 3 rather than lower.

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+resource ("Render the drawing to an image file") and adds a distinguishing rationale ("so it can be inspected without AutoCAD"), which no sibling tool provides. An agent can immediately tell this is the visual-output/export tool. It is clearly separable from the many create/query/edit siblings.

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 gives the operative context: rendering is used to inspect the drawing without AutoCAD, and it distinguishes the two execution paths (ezdxf headless vs COM screenshot) and the prerequisite "preview" extra. There is no other render/preview sibling to route against, so no explicit alternative is needed, but it stops short of stating when-not-to-use or any precondition about an active document/connection.

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