archicad_create_slabs

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

Annotations declare a non-read-only, non-destructive, non-open-world operation, and the description adds the crucial recovery hint ('Revert with archicad_undo') plus the batch/global-geometry semantics that annotations cannot convey. It still omits permissions, rate limits, and what happens to the created layer on failure.

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 tightly packed sentences, zero filler, with the core capability front-loaded and the recovery instruction appended last.

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 6-parameter batch mutation with no output schema, the description covers purpose, geometry model, layer behavior, and reversibility. Minor gaps: floorIndex is unexplained and no hint of the dryRun return shape is given, though the schema handles dryRun.

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?

With 67% schema coverage, the description meaningfully clarifies that 'top level and thickness' are exact values applied uniformly across the batch ('homogeneous'), which disambiguates the global topLevel/thickness parameters. It does not address floorIndex or the dryRun toggle, which the schema partially covers.

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?

States a specific verb ('Creates'), resource ('slabs'), and scope ('many homogeneous ... at once'), with concrete use cases (site blocks, platforms, masses). It is clearly distinguishable from the single-slab sibling CreateSlabs and from archicad_create_meshes.

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 parenthetical use cases imply when this tool fits (bulk massing/site geometry), and 'Revert with archicad_undo' gives a recovery path. However, it never explicitly contrasts with CreateSlabs or Archicad's other creation tools, so selection guidance is only implied.

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