draw_polyline

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

No annotations are provided, so the description carries the full behavioral burden. It notes that the layer is auto-created if missing, which is useful, but omits whether the operation requires an active drawing/connection, whether it is undoable, and any mutation effects. For a drawing-mutation tool with zero annotation coverage this is a significant gap.

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 purpose sentence is front-loaded, followed by a compact Args section with no filler. Sizing is appropriate for a five-parameter tool.

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 values need not be explained, and parameters are well covered. However, for a mutation tool with no annotations, the description leaves behavioral and precondition gaps (connection state, undo semantics) that an agent would want.

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%, so the description must compensate, and it does: the Args block documents all five parameters, including that vertices requires at least 2 points, that layer is auto-created, and that color is an ACI value in range 1-255. These add real semantics beyond the bare schema types.

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 (Draw) and resource (LWPOLYLINE polyline through vertices), and the LWPOLYLINE specificity distinguishes it from siblings like draw_line and draw_arc. An agent can tell apart this tool from generic line-drawing alternatives without opening the schema.

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?

No guidance on when to use draw_polyline vs draw_line or draw_arc, or on prerequisites like an active connection. The usage context is implied by the name alone, with no explicit alternatives or exclusions.

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