create_ngon

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

Annotations already mark the tool as destructiveHint=true and readOnlyHint=false, but the description adds no behavioral context beyond the bare word 'Create'. It does not explain what is destroyed, whether an existing object is overwritten, or how the spline is inserted into the scene.

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, front-loaded, and free of filler. It states the core purpose first and then the two key parameters, making it easy for an agent to parse quickly.

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 tool with 17 parameters and no output schema, this description is too thin. It never explains why the schema contains parameters for Text, Arc, Helix, Donut, and Rectangle, or whether those are accepted and ignored. The destructiveHint annotation is also left unexplained.

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 schema already documents all 17 parameters with descriptions, so the baseline is 3. The description adds no new meaning beyond what the schema states for radius and sides, and it does not clarify which of the many unrelated parameters (Arc, Text, Helix, Donut, Rectangle) should be ignored for an NGon.

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 states a specific verb and resource: 'Create a regular polygon (NGon) spline.' It distinguishes the tool from siblings like create_circle and create_rectangle by addressing the NGon primitive directly.

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 usage context is implied: use this when creating a regular polygon spline. However, it does not explicitly say when not to use it or which sibling tools cover other spline shapes, so the agent is left to infer the alternatives.

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