get_node_info

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

With no annotations, the description carries the burden. It discloses the type of information returned (publications, subscriptions, services) and mentions the transport mechanism ('pure Rosbridge WebSocket API'), adding some context. However, it does not describe error behavior, safety profile, or any operational constraints beyond these hints.

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 sentence of 12 words, front-loaded with the verb 'Inspect'. Every word is useful; there is no redundancy or filler.

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 is simple with one parameter, and the existence of an output schema covers return value structure. However, missing parameter semantics and usage guidance leave the description incomplete for an agent to confidently invoke the tool in varied contexts.

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 0%, so the description must compensate for the single required parameter 'node'. It does not explain the expected format, naming convention, or provide examples. The word 'node' in the description suggests it refers to a ROS node, but that is a weak inference, not sufficient semantic guidance.

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 uses a specific verb ('Inspect') and resource ('ROS node details') and enumerates the exact information included (publications, subscriptions, services). It clearly distinguishes from sibling tools like list_nodes (which lists nodes) and echo_topic (which streams messages).

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 a specific node's details, which is clearer than list_nodes, but it does not explicitly state when to use it over alternatives or mention exclusions. No when/when-not guidance is provided.

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