create_edge

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

No annotations; description only says 'create' without mentioning effects on existing geometry, visibility, or whether points must be on existing geometry. Lacks behavioral context.

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?

Single sentence with 11 words is concise, but lacks structure (e.g., no bullet points or usage hints). Could be improved with minimal expansion.

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 simple tool with 3 parameters and no output schema/annotations, the description is too minimal. Leaves agent uninformed about behavior, constraints, or return values.

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 covers 67% of parameters; description adds no extra meaning beyond what's in the schema. The 'layer' parameter is undocumented in description, and no details on coordinate units or allowed values.

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?

Clearly states 'create' verb and 'line segment (edge)' resource; distinguishes well from sibling tools like create_face or create_box by specifying it's between two 3D points.

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 this tool vs alternatives like create_face (which also creates edges). No exclusions or prerequisites mentioned.

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