scene-create_object

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

With no annotations, the description must disclose behavioral traits. It only states the action (create) without mentioning side effects, whether the new object becomes the active/selected one, if it requires an active scene, or any limitations. The description is too thin 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?

The description is a single sentence with no redundant words. It is appropriately sized for the tool's simplicity and front-loads the core purpose.

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?

The tool has 3 parameters, no output schema, and no annotations. The description fails to provide essential context such as success/failure behavior, return values, prerequisites (e.g., active scene), or examples. For a creation tool, more information is expected to ensure correct invocation.

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 0%, meaning the description adds nothing about parameters. The schema itself provides titles for parameters (e.g., 'Primitive type', 'World location'), so the agent can infer meaning, but the description fails to compensate for the low coverage as required. It doesn't explain how parameters affect behavior or any defaults.

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 clearly states the tool creates a primitive object in the scene, using a specific verb and resource. It distinguishes from general object creation (object-create) by limiting to primitives, though it doesn't explicitly name alternatives.

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 other creation tools like object-create, geometry-create_curve, or volume-create_empty. The sibling list includes many creation tools, and without context, an agent cannot decide which one is appropriate.

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