Set a node's advertised location

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

Annotations already declare this tool as idempotent and non-destructive. The description adds the home node behavior and CLI equivalent, but doesn't provide additional behavioral context beyond what annotations cover.

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?

Two sentences cover purpose, usage, and equivalent command with no wasted words. Information is front-loaded and each sentence earns its place.

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 4 parameters and an output schema. The description covers the core purpose and key usage hint. It is nearly complete, though it could mention lat/lon bounds or validation.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the 'node' parameter's default behavior (omit for home) and clarifying that lat/lon are in decimal degrees, going beyond the schema.

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 verb 'Set' and resource 'node's advertised lat/lon', adding specificity about decimal degrees and distinguishing it from sibling tools like set_tx_power or set_contact_path.

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 provides clear usage guidance by noting that omitting the 'node' parameter targets the home node. It also gives an equivalent CLI command, but does not explicitly mention when not to use this tool.

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