add_cubes

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

No annotations provided; description fully bears the burden. It discloses efficiency, array structure, symmetric building advice, and return value (all created cubes with face UVs), adding useful context beyond basic functionality.

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?

Front-loaded with purpose, then adds usage tips. Slightly verbose but every sentence is informative; could be tightened.

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?

With one parameter, no output schema, and no annotations, the description covers purpose, parameter details, usage guidance, return value, and common pitfalls thoroughly.

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% but description adds meaning by detailing that each item takes fields like add_cube, and provides guidance on symmetric parts and Z-fighting, which is beyond schema.

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 'Create many cubes in one call — the efficient way to author a detailed model', clearly indicating verb (create) and resource (cubes), and distinguishes from add_cube by emphasizing bulk efficiency.

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?

Explicitly advises aiming for 20-50+ cubes and not 6-8, and provides tips on symmetric parts and Z-fighting avoidance. Alternative add_cube is implied but not explicitly mentioned.

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