Trigger a node's neighbour discovery

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

The description discloses that the tool sends a broadcast request that populates a neighbor list (a write operation), consistent with readOnlyHint=false and destructiveHint=false. It adds context beyond annotations by explaining the side effect and how to retrieve results, but does not cover failure modes or rate limits.

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?

Three concise sentences with no filler. The primary action is stated first, followed by outcome and alternative invocation. Every sentence provides value.

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 covers the core action and result, and references sibling tools for reading neighbors. With an output schema present, it does not need to detail return values. Minor gaps: no mention of error scenarios or idempotency, but adequate for a simple tool.

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 coverage is 100% with descriptions for both parameters. The description repeats that 'node' is required and references the admin command, but adds minimal new semantic detail beyond the schema. Baseline of 3 is appropriate.

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 ('broadcast') and resource ('node-discovery request'), clearly indicating the action. It distinguishes from sibling tools like 'admin' by stating it is equivalent to 'admin <node> discover-neighbors', and references 'get_node_neighbors' for reading results.

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 mentions that the tool is equivalent to an admin command and requires a node, but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like 'admin' or other discovery tools. It lacks exclusions or context for selection.

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