object-create

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only says 'Create' and does not explain whether the object is added to the active scene, any side effects, permissions, or what the result/return value is.

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, efficient sentence with no filler. However, it is under-specified for a tool with this many parameters and behavioral implications, so brevity sacrifices necessary detail.

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?

This is a high-complexity 18-parameter creation tool with no output schema and no annotations. The one-sentence description is far too minimal to help an agent understand type-specific parameters, defaults, placement behavior, or expected outcomes.

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 18 parameters and 0% schema description coverage, the description provides no parameter semantics. It does not mention that `type` selects the primitive, nor explain primitive-specific parameters like radius, vertices, rotation, or location.

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 uses a specific verb and resource: 'Create a common mesh primitive or empty.' It clearly conveys the core function. However, it does not distinguish this from other creation tools in the sibling list such as light-create, camera-create, or volume-create_empty.

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 guidance about when to use this tool versus alternatives like object-duplicate, mesh-fill, or geometry_create_curve. No preconditions, scene context, or exclusions are mentioned.

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