rename_device

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

Beyond the annotations, the description discloses persistence of the name, the stripping of double quotes and non-printable characters, and the fact that the identifier is looked up in the active lease table. These are behavioral details not present in the annotations, and there is no contradiction with the annotation hints (idempotentHint, destructiveHint false).

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 tightly structured: purpose first, then parameter semantics, a critical sibling note, and examples. Every sentence earns its place—no filler or repetition of schema content. The format is readable and front-loads the most important information.

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 (2 params, output schema present, annotations provided), the description covers all necessary context: what it does, how to identify the device, the new name constraints, and how it relates to sibling tools. Nothing an agent needs to call it correctly is missing.

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?

The input schema already has 100% coverage for both parameters, so the baseline is 3. The description adds extra meaning by explaining that identifier can be an IP, MAC, or name fragment and is resolved via the active lease table, and by giving concrete examples of valid invocations. This goes beyond the schema's terse descriptions.

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 states a specific verb and resource: 'Give a device a persistent DISPLAY name on the router'. It also differentiates from siblings by explicitly noting that set_static_lease and pin_device do NOT change the display name, making it unmistakable what this tool uniquely does.

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?

It gives explicit when-to-use guidance by stating that the display name is set ONLY by this tool and that sibling tools do not affect it. Examples further clarify correct invocation patterns, leaving no ambiguity about when to choose this tool over alternatives.

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