create_slab

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

No annotations are provided, so the description carries full burden. It mentions 'Units: mm' but does not disclose whether the tool modifies the document, requires permissions, is undoable, or handles errors like non-closed polygons. Critical behavioral traits are missing.

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 short, front-loaded sentences with no redundant information. Every phrase adds value: the action, the input type, the constraint, and the unit.

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 moderate complexity (3 parameters, output schema exists, no annotations), the description covers the core action and input constraints but lacks details on coordinate systems, error states, return values, and integration with sibling tools. It is adequate but not thorough.

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 description must compensate. It adds meaning for 'outline' by stating it is a polygon with minimum 3 points, but does not describe 'thickness_mm' or 'layer' beyond schema. The added context is partial.

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 the verb 'Create', the resource 'slab element', and the input 'from a polygon outline'. It distinguishes this tool from siblings like create_beam or create_wall by specifying the unique input type (polygon outline) and minimum points requirement.

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 description provides a usage constraint ('Minimum 3 points') but does not explain when to use this tool versus alternatives (e.g., create_beam, create_column). No guidance on when not to use it or prerequisites is given.

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