create_ros2_lidar_publisher

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add useful context: the tool has preview/create dual behavior, depends on a previously created LiDAR prim, automatically resolves the owned render product, and supports an explicit override. However, it does not disclose side effects of creation, whether preview is non-mutating, or what happens to existing publishers, topics, or runtime state.

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 action. The first sentence states what the tool does, and the second sentence provides a key dependency and override behavior without filler. Some terminology could be clearer, but the length is appropriate and every sentence contributes useful 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 13-parameter creation tool with no annotations and 0% schema parameter coverage, the description is incomplete. It covers a prerequisite and one override but omits the meaning of most parameters and does not explain what preview versus create actually does in practical terms. The presence of an output schema mitigates missing return-value details, but not the large parameter and behavior gaps.

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% and there are 13 parameters, so the description must compensate. It adds meaning for only two parameters: lidar_prim_path (must exist, created by create_lidar) and render_product_path (explicit override for external render products). The remaining parameters such as preview, domain_id, topic_name, qos_profile, node_namespace, frame_id, and lidar_type receive no semantic 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 action ('preview or create') and a specific resource ('ROS2RtxLidarHelper publisher' for an MCP RTX LiDAR runtime). It is distinguishable from sibling ROS2 publishers (clock, TF, camera, joint state) because it is explicitly LiDAR-focused. The mention of create_lidar and render_product_path makes the tool's domain concrete, though the runtime naming is somewhat jargon-heavy.

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 provides a clear prerequisite: the LiDAR prim must first be created with create_lidar. It also explains when render_product_path is relevant as an override for externally-created render products. However, it does not state when to choose this tool over sibling ROS2 publisher tools or when preview should be used instead of create, leaving some routing decisions implicit.

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