make_drawing

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

The annotations already disclose that the tool is destructive, non-idempotent, and not read-only, so the safety profile is mostly covered. The description adds useful unit conventions and indicates that verified measurements and error evidence are available, but it does not explain the overwrite behavior beyond the schema, required document state, or what file is actually produced.

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 short and front-loads the creation intent, but the opening sentence is vague and the closing sentence about measurements/error evidence is underspecified. It avoids bloat but leaves key details unclear.

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 destructive drawing-creation tool with a required path, no output schema, and only partial schema coverage, the description is too thin. It should clarify what input is required, what gets written, and how overwrite interacts with existing output.

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 coverage is 50%: the overwrite parameter is well documented in the schema, but the required path parameter has no description there and is not explained in the tool description. The description does not say whether path is the source model, destination drawing, or both, so it fails to compensate for the schema gap.

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?

"Make drawing" largely restates the tool name and does not specify what is being drawn, whether it creates a drawing document from a part/assembly, or what the output path represents. The only substantive additions are the engine name and unit conventions, which do not clarify the core action or distinguish it from siblings such as export or screenshot.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites such as an open document or source model, and no indication of when not to use it. The mention of inspecting measurements and error evidence hints at a workflow but does not tell the agent when this tool is appropriate.

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