create_face

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

No annotations provided, so description bears full burden. It discloses unit behavior (inches unless metric) but does not explain what happens with invalid points (non-coplanar, self-intersecting), error conditions, or response format. Insufficient for a creation tool.

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 concise sentences with no filler. First sentence states purpose, second adds critical unit context. Front-loaded and efficient.

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?

No output schema, so description should explain return value (likely entity ID) and error handling. Lacks details on behavior for invalid input (e.g., non-coplanar points). With 3 params and no annotations, description is adequate but not comprehensive.

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. Description adds value by clarifying that points are in SketchUp's default unit (inches unless metric), which is not in schema. This helps agents provide correct coordinates.

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 the action (Create), resource (flat face/polygon), and constraints (ordered 3D points). Distinguishes from sibling tools like create_box, create_circle, etc. by specifying 'flat face (polygon)' and 'ordered list of 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?

Implies usage for creating polygon faces from points, but no explicit guidance on when to use this tool versus alternatives like create_polygon or create_edge. 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.