clean_all_ros2_nodes

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

Description clearly states that the tool terminates running processes, which is a destructive action. Without annotations, it effectively communicates the behavioral impact, though could add caution about other sessions.

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?

Single sentence with 13 words, no superfluous information. The verb 'kills' is upfront, making the action clear immediately.

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 the tool's simplicity (no inputs, no output schema), the description fully covers its operation: what it kills and for what purpose (clean environment). No gaps.

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?

Tool has no parameters, so description does not need to add parameter info. Schema coverage is 100% trivially. Baseline for 0 parameters is 4.

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?

Description uses specific verb 'kills' and resource 'ROS 2 and Gazebo related processes', clearly stating the tool's purpose. It distinguishes from sibling tools which are more specific (e.g., list_ros2_nodes, launch_gazebo).

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?

No explicit guidance on when to use or when not to use this tool. It does not mention alternatives or prerequisites, leaving the agent to infer usage context.

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