Read a remote node's recent neighbours

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. Description adds useful behavioral context: returns up to 8 neighbors in a specific format, mentions the companion firmware limitation ('can't target home'), and notes the data source. No contradictions with annotations.

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?

Description is concise (three sentences) and front-loaded with the core purpose. Every sentence adds value: purpose, context, equivalent command, pairing with sibling. No redundant or vague phrasing.

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 (two parameters, annotations cover safety, output schema exists), the description is complete. It explains the return format, pairing with sibling, and data source. No missing critical details.

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. Description adds minimal extra context for `node` (companion firmware limitation) but does not address `dryRun`. Baseline of 3 is appropriate as schema does the heavy lifting.

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 clearly states 'List a remote repeater's recent neighbours (up to 8)' with a specific verb and resource. It distinguishes from sibling `discover_neighbors` by mentioning it pairs with an active probe. Also notes equivalence to `admin <node> neighbors`, reinforcing the purpose.

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?

Description provides clear context: it is the H15 topology data source and pairs with `discover_neighbors(node)` for fresh data. It implicitly advises when to use each tool. However, no explicit when-not-to-use statements are given.

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