create_camera

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only tells the agent that a camera is added and describes some parameter meanings, but it does not disclose whether an existing camera at prim_path is overwritten, whether the operation is idempotent despite the idempotency_key parameter, or what side effects occur in the scene.

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 compact and front-loaded with the main purpose, followed by a tight bullet list of arguments with no filler. Each sentence adds information.

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?

For a creation tool with 6 parameters, no annotations, and zero schema-level descriptions, the definition is incomplete. It fails to explain the two infrastructure parameters and omits key behavioral details like overwrite semantics and scene mutation impact, leaving an agent to guess important call context.

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 does add meaningful semantics for prim_path, position, rotation, and resolution, including units and a default, but command_id and idempotency_key are left completely unexplained.

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 states a specific verb and resource: 'Add a camera sensor to the scene.' This clearly distinguishes the tool from camera-related siblings like create_ros2_camera_publisher or capture_camera_output, which serve different purposes.

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 explicit guidance about when to use this tool versus alternatives such as create_lidar, delete_sensor, or capture_camera_output. The intended usage is only implied by the tool name and one-line purpose, with no exclusions or contextual routing.

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