create_object

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

With no annotations, the description must carry behavioral disclosure. It only states 'Create a new object' without describing side effects like selection state, scene mutation, or error conditions. It does not mention that the object is added to the current scene or that transform defaults apply.

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 followed by a clear bullet list. It is front-loaded with the primary purpose and contains no redundant 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?

The description covers the core action and all parameters with useful semantics. However, it omits details such as the return value or post-creation state (e.g., selection), and does not mention that the tool operates on the active scene. Given no annotations or output schema, this is a minor gap.

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 description adds meaning beyond the schema by explaining location as 'world position', rotation as 'Euler rotation in radians', and scale as 'scale factors'. It also lists valid object types, though using 'etc.' and not exhausting the full list. It does not describe defaults or constraints beyond the 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?

The description clearly states 'Create a new object of any type with optional transform,' specifying the verb and resource. It is distinguishable from specialized creation tools like create_curve or create_camera, though it doesn't explicitly mention them as 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 specialized creation tools. It does not mention alternatives or conditions for selection, leaving the agent to infer.

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