get_ros2_status

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

There are no annotations, so the description carries the full burden. The verb 'Read' clearly signals a non-mutating operation, and the listed items (bridge/core/nodes, domain source, distro, workflow count) clarify the scope. It does not mention any side effects, but none are implied.

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 a single, tight sentence with no filler. It front-loads the action and resource, then enumerates the specific status fields in a compact list.

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 reasonably complete for a read-only status tool and an output schema exists for return values. However, the undocumented parameters and the lack of guidance relative to several sibling status tools leave the agent to guess about invocation details and selection criteria.

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?

The schema documents two optional parameters, command_id and idempotency_key, but the description mentions neither. With 0% schema description coverage and no compensation in the description, an agent has no clues about the meaning or purpose of these parameters.

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 an action ('Read') and a specific resource: ROS 2 bridge/core/nodes state, including domain source, distro, and workflow count. This distinguishes it from generic status siblings like get_runtime_status, though it does not explicitly name 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?

The description implies the tool is for inspecting ROS 2 state and workflow counts, but it provides no explicit guidance on when to prefer it over get_runtime_status or the numerous other status/workflow tools. Usage is inferred rather than stated.

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