echo_topic_messages

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

With no annotations, the description must disclose behavioral traits. It does not state whether the tool blocks until messages arrive, what happens if the topic doesn't exist, or if it has side effects. It only says 'capture and return', which is minimal.

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-loaded with purpose. The Args/Returns section is somewhat redundant with schema but not harmful. It could be more concise by omitting schema-repeated details, but overall it's efficient.

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?

Given an existing output schema and 2 well-documented parameters, the description is adequate for basic usage. However, it lacks context on practical aspects (timeouts, error handling, real-time behavior) that would make it complete for a production agent.

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 coverage is 100% (both parameters described in schema). The description does not add extra semantic detail beyond the schema; it merely restates parameter names and default. Baseline 3 is appropriate.

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 action: 'Capture and return messages from a ROS2 topic.' The verb 'capture and return' combined with resource 'messages from a topic' is specific and distinct from siblings like 'get_topic_info' (metadata) or 'get_topic_frequency' (rate).

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 capturing a specified number of messages from a topic, but it lacks explicit guidance on when to use this tool over alternatives (e.g., blocking vs non-blocking, real-time vs sampling) and does not mention when not to use it (e.g., for high-frequency topics).

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