Add a cube

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that "to is the exclusive upper bound" and that origin defaults to from, which are non-obvious semantics. However, it says nothing about prerequisites (an open project), which scope the cube is added to, or undo behavior for a mutating operation.

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 the core action, then parameter guidance. Two efficient sentences with the coordinate-system caveat placed where it matters. Little wasted text.

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 14-parameter mutation tool with no annotations and no output schema, the description covers the geometry essentials but leaves many parameters undocumented in both schema and text. Adequate but with clear gaps given the complexity.

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 only 21%, so the description must compensate. It explains from, to, size, origin default, and texture/faces/autouv behavior, but omits name, color, box_uv, parent, inflate, rotation, and uv_offset entirely. Partial compensation over a low-coverage 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?

"Create a cube element" states a specific verb and resource, so the agent can distinguish this from mesh/group/element creation siblings. It doesn't explicitly name an alternative (e.g., bb_add_mesh or bb_add_element), so sibling differentiation is implied rather than stated.

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?

There is no when-to-use guidance and no alternative named. The only routing-like text is "Provide from+to, or from+size," which is a parameter constraint rather than usage context. An agent gets no help deciding between this and bb_add_element/bb_add_mesh.

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