ros_topic_status

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

描述直接说明了执行的具体命令 (`rostopic hz -w 5` 与 `rostopic echo -n 1 --noarr`)，这比仅说“查询状态”更具透明性。在无 annotations 的情况下，它补充了实际行为、容器内执行和示例话题，可让agent预知操作和影响，只是未详细谈延迟或失败模式。

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?

描述紧凑且信息密度高：第一句即说明工具目的，随后给出底层命令、参数格式和真实用例。没有冗词，所有句句都有价值。

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?

该工具参数少、行为简单，描述覆盖了核心所需：命令、参数、示例和成功判断。已有输出 schema 可承载返回值信息，因此描述无需再解释返回格式。整体对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 只写着 topic: string，没有任何说明，schema_description_coverage 为 0%。描述对此做了补偿：指出这是完整话题名，并给出具体示例。对于一个参数的工具，这足以让agent正确填写。

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?

描述明确了操作：查询 ROS 话题状态，并说明输出是采样频率(hz) 和最新消息摘要，这比工具名更具体。虽然与兄弟工具 ros_topic_echo 没有明确对比区分，但从用途上可以判断它面向状态/频率检查而非持续 echo，因此足够清晰。

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?

描述了适用场景：验证 ego-planner 重启是否成功，并给定了判断标准（occupancy 有 hz 即成功）。这为agent提供了明确的上下文，虽然没有明确排除替代工具，但已经超过模糊用法，符合“clear context, no exclusions”。

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