monitor_topic

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 mentions 'collects messages over time' but does not describe blocking behavior, return format, or the interaction between duration and message_count (e.g., 'whichever comes first' is only in schema). The agent is left guessing about side effects or output expectations.

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 two sentences, directly states the core action and purpose, and contains no filler. Every word contributes to understanding the tool's function. It is appropriately sized for maximal clarity with minimal text.

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 tool has no output schema and no annotations, so the description must itself supply context about behavior and results. It does not mention what happens after the duration ends, what is returned (e.g., collected messages), or the stopping condition based on message_count. Given the tool's moderate complexity, this is a significant gap that leaves the agent underinformed.

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 100%, so the parameters are fully documented in the schema. The description adds no parameter-level details beyond what the schema already provides, which matches the baseline of 3 for high coverage. No additional value from the description on this dimension.

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 clearly states the tool's function: 'Monitor a ROS 2 topic for a specified duration.' The verb 'monitor' distinguishes it from siblings like 'publish_to_topic' or 'list_ros_topics', and the phrase 'for a specified duration' sets it apart from one-off queries. This is a specific verb+resource combination with clear differentiation.

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?

The description implies usage for observing messages over time with a duration limit, but it does not explicitly state when to use this tool versus alternatives like 'get_topic_info' or 'list_ros_topics'. There are no exclusions or comparator references, leaving the agent to infer context from the tool's name and sibling list.

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