create_ros2_camera_publisher

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

With no annotations, the description carries the full behavioral burden. It discloses automatic resolution of the owned render product and the override path, which is useful. However, it does not explain side effects of creating the publisher, any idempotency/retry behavior, or what 'preview' actually does at runtime.

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 three compact sentences with no filler. The primary purpose is front-loaded, and the prerequisite/override guidance is tightly packed into the remaining sentences.

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 13-parameter creation tool with no annotations, this description is too sparse. The existing output schema does not cover parameter semantics, and major aspects like preview/run distinction, default publishing behavior, and parameter effects are left unexplained.

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 for fully undocumented parameters. It only adds meaningful context for camera_prim_path and render_product_path, leaving 11 of 13 parameters (including preview, topic_name, qos_profile, camera_type, and use_system_time) without any behavioral explanation.

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 names a specific verb ('Preview or create'), a specific resource ('ROS2CameraHelper publisher'), and the runtime context ('MCP camera runtime'). This clearly distinguishes it from sibling ROS2 publisher tools like create_ros2_tf_publisher or create_ros2_lidar_publisher.

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?

It explicitly states that the camera prim must be created first with create_camera, providing a clear prerequisite and workflow context. It also explains when to use render_product_path as an override, though it does not contrast when to use preview vs create or when to prefer it over alternative publisher tools.

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