cad_sketch_polyline

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

Discloses auto coincident-joins, closed loop, auto_hv constraints, and ground_first behavior. Returns line ids. No annotations provided, so description carries burden. Missing context on sketch state requirements.

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?

Three concise sentences: overall action, options, return value. No redundancy. Front-loaded with main purpose.

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?

Covers core functionality and all boolean options. Missing details on sketch context (e.g., whether sketch must be active), error cases, or interaction with existing sketch entities. Adequate for a sketch tool.

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?

Explains points array, closed, auto_hv, and ground_first with specific meanings beyond schema (e.g., 'closes the loop', 'applies horizontal/vertical'). schema coverage 0%, so description compensates well, except sessionId is not explained (likely understood from context).

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?

Description clearly states it adds a chain of lines through points, distinguishing it from single line (cad_sketch_line) and other sketch tools. The verb 'Add' and resource 'chain of lines' are specific.

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?

Implies usage for multiple connected lines, but does not explicitly compare to siblings like cad_sketch_line or cad_sketch_rectangle, nor when not to use it. No alternatives mentioned.

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