object_create

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by saying name/transform/parent/attributes are applied 'right away' at creation (one round trip instead of two), but stays silent on collision behavior for duplicate names, error conditions, or undo.

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?

One sentence, front-loaded with the verb and the class enumeration, with the optional-field behavior appended. The class list is long but every item is functional information rather than filler.

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?

Return values need not be described because an output schema exists. Given that annotations cover the safety profile and the description covers creation semantics and accepted classes, what remains missing is mostly parameter formatting already implied by the schema's array/object types.

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%, so the description carries the full burden and only partially delivers: it maps position/rotation to a 'transform' and names parent and attributes, but gives no formats (array length for position, Euler vs quaternion for rotation) and never explains that parent accepts either an integer or a string handle despite that ambiguity in 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?

States a specific verb and resource (create a scene object) and enumerates the exact class values accepted, which lets an agent distinguish it from material_create or baker_create. It does not, however, distinguish itself from the sibling light_create and camera_create tools even though LightObject and CameraObject are listed as valid classes here.

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 when-to-use or when-not-to-use guidance is given. The most important routing question an agent faces — should I call object_create with 'LightObject' or call light_create? — is left completely unresolved, and nothing states whether this is preferred over create-then-object_set_transform.

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