ros2_record_and_inspect

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 says it records messages for a period and returns stats, but it does not disclose whether the call blocks until duration_sec elapses, whether it writes data to disk, what side effects occur, or what the returned summary statistics cover.

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 short and front-loads the core behavior. The Args list is clean and each line is purposeful, though it partially duplicates parameter names with minimal expansion.

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?

The description is minimally viable for a simple three-parameter tool and an output schema exists, so return values need not be explained. However, with no annotations and no usage guidance, it leaves open questions about execution behavior, topic type formatting, and when this tool is the right choice among siblings.

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 Args section must carry the load. It adds basic meaning: topic is what to record, topic_type is the message type, and duration_sec is in seconds. However, it omits format guidance such as fully-qualified topic names or ROS message type syntax, leaving a meaningful gap.

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 action, 'Record topic messages for a period,' and a clear result, 'return summary statistics.' This is enough to distinguish it from siblings like ros2_topic_echo or ros2_measure_topic_hz, though it does not explicitly name those alternatives.

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 on when to use this tool versus the many sibling tools. The description does not mention when summary statistics are preferable to live echo, frequency measurement, or assertion tools, nor does it explain any prerequisites for recording.

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