create_cube

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

With no annotations provided, the description must fully disclose behavioral traits. It fails to mention that the tool creates a new cube body, any side effects (e.g., overwriting existing objects), or required permissions. The description is completely insufficient for a mutation 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?

Though very short, the description is under-specified rather than concise. It fails to convey essential information, so it does not earn its place. A concise description would pack more meaning into few words.

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 tool has 8 parameters, no output schema, and no annotations, the description is critically incomplete. It does not explain the overall behavior, how the cube is placed, the role of body_name, or any default behaviors. The description is inadequate for an agent to use the tool correctly.

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 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides (e.g., size, center coordinates, placements). No value is added, but no error is made.

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 'FreeCAD tool: create_cube' is nearly a tautology, merely restating the tool name. It does not specify the action (create a cube) or the resource (e.g., a body in a FreeCAD document). Siblings like create_cylinder or create_sphere have similar descriptions, so no differentiation is possible.

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?

No guidance is given on when to use this tool versus its many siblings (e.g., create_box, create_cylinder). There is no mention of prerequisites, context (e.g., active document or body), or scenarios where this tool is preferred.

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