get_node_connections

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

No annotations are provided, so the description carries full burden. It clearly indicates a read operation (via 'Get'), but it does not disclose behavior on missing nodes, whether the output includes only active topics, or any permissions required. For a read-only tool, this is acceptable but not rich in behavioral detail.

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, front-loaded sentence with no wasted words. It immediately states what the tool does and is appropriately concise for the tool's simplicity.

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?

For a simple tool with one parameter and no output schema, the description states the core functionality completely. It lacks details about return format or error behavior, but given the low complexity, the description is sufficient for an agent to select and invoke the tool correctly.

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 covers 100% of the parameter (node_name), so baseline is 3. The description adds minimal extra meaning by implying node_name is the subject of the connection query, but it does not provide additional format or constraints beyond the schema already provides.

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 tool's function: retrieving all topics a node publishes to and subscribes from. It uses a specific verb ('Get') and resource ('all topics that a node publishes to and subscribes from'), which distinguishes it from sibling tools like get_topic_info or monitor_topic.

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 when you need a node's publish/subscribe connections, but it does not explicitly state when to choose this over alternatives, nor does it provide exclusions or prerequisites. The single parameter node_name is straightforward, but guidance on comparisons with other topic-related tools is absent.

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