create_ros2_tf_publisher

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

With no annotations, the description carries the full burden of disclosing side effects, but it only states that the tool can preview or create. It does not explain whether creation replaces an existing publisher, registers a persistent workflow, or requires an idempotency key, nor what preview returns; the meaning of '6.0-style' is also left opaque.

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 with no filler, which is efficient. However, it is under-specified rather than appropriately concise, relying on unexplained jargon and omitting essential clarifiers that would justify its brevity.

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 tool with 11 parameters, no annotations, and zero schema coverage, this description is critically incomplete. It does not explain required inputs, optional behavior, return values, or how this integrates with ROS2 workflows, so an agent cannot reliably invoke it correctly.

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 was expected to compensate for the schema's silence, but it provides no explanation for any of the 11 parameters. graph_path, target_prims, topic_name, qos_profile, static_publisher, and the other arguments remain completely undocumented.

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 ('6.0-style ComputeTransformTree to ROS 2 TF publisher'), which distinguishes it from sibling ROS2 publisher tools like create_ros2_clock_publisher or create_ros2_joint_state_publisher. It loses a point because '6.0-style' is unexplained and the relationship between ComputeTransformTree and the publisher is left vague.

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 guidance about when to use this tool over the many sibling ROS2 workflow tools, nor about when to choose preview versus create mode. No alternatives, conditions, or exclusions are mentioned, leaving the agent without selection criteria.

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