Create Polyline

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

The description labels it 'lightweight 2D polyline', adding some behavioral context. However, it doesn't disclose side effects, permissions, or other traits beyond what annotations provide (readOnlyHint=false). No contradictions.

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?

Two sentences and an example, all front-loaded. No wasted words; every part adds value.

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?

Given the tool has 4 parameters, an output schema (context signal), and a straightforward purpose, the minimal description is adequate but lacks depth. No guidance on context or edge cases. Could mention that the polyline is created in the current drawing.

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 100%, so baseline is 3. The example adds slight value by showing 'points' and 'closed' usage, but doesn't explain parameters like 'color' or 'layer' beyond the schema. The description does not significantly enhance parameter understanding.

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 'Create a lightweight 2D polyline through the given points' with a specific example. It uses a strong verb-resource pairing and distinguishes from siblings like entity_create_line by specifying polyline and including 'lightweight 2D' qualifier.

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 explicit guidance on when to use this tool versus alternatives like entity_create_line or entity_create_rectangle. The example implies it's for arbitrary polylines, but no when-not or alternative tools are mentioned.

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