register_scene_instance

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

No annotations are provided, so the description must carry full weight. It mentions efficiency and return values but fails to disclose whether the tool creates or updates instances, side effects, permissions, or behavior when instance_id is provided versus omitted.

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 concise sentence that front-loads the core action and return values. It is not verbose, but given the tool complexity, it could benefit from additional structured details without becoming lengthy.

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?

With 11 parameters, no annotations, and an output schema not elaborated, the description lacks completeness. It does not explain the relationship between registering and moving (e.g., instance_id determines action), nor does it cover required versus optional parameters or error scenarios.

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 must compensate. It only implies x_mm and y_mm are position coordinates, but provides no meaning for the 9 other parameters like rhino_guid, scale, locked, or room_id, leaving the agent with only parameter names to infer functionality.

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 registers or moves an asset instance in millimetres without retransmitting full metadata, which is a specific verb+resource action that differentiates it from sibling tools like place_diagram_asset.

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?

The description implies usage for efficient placement or movement but does not explicitly state when to use this tool versus siblings like place_ikea_furniture or validate_scene_layout, nor does it mention when not to use it.

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