create_primitive

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

No annotations exist, and the description does not disclose behavioral traits such as whether the primitive is added to the scene, any default settings, or potential side effects. The minimal phrase 'Create mesh primitive' provides no insight beyond the name.

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?

The description is a single terse sentence, which is efficient in length but severely under-informative. Every tool description should earn its words; this one does not provide sufficient detail to be useful.

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?

Despite the presence of an output schema and a single ambiguous parameter, the description offers no explanation of return values, primitive customization, or any contextual details needed for effective use. It is completely inadequate for a tool with no annotations.

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?

The only parameter, 'kwargs', has zero schema description and the description does not explain its purpose, structure, or expected values. With 0% schema coverage, the description fails to compensate, leaving the parameter entirely opaque.

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 a clear verb ('Create') and resource ('mesh primitive'). It distinguishes this tool from siblings like 'create_camera' and 'create_three_point_lighting', but the term 'primitive' is somewhat vague without specifying which primitives (e.g., cube, sphere).

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 provided on when to use this tool versus alternatives (e.g., import_asset, create_camera). The description lacks any context about prerequisites or exclusions.

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