name_device

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

Annotations already cover the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), and the description adds the crucial scoping fact that changes stay in the local registry and never touch the router. The clear-vs-omit semantics also imply how repeat calls behave. It does not mention permissions or error behavior when the device is unknown.

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 tight blocks: the scope statement first, then the parameter convention. No filler. Slightly fragmentary ('device: MAC, ...'), but every 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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Still, for a 5-parameter mutation tool the description omits whether the device must already exist, what tags accept, and what happens on a bad identifier — gaps an agent would want closed.

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 coverage is 0%, so the description must carry parameter meaning. It does explain the `device` parameter's accepted forms (MAC, current nickname, router name or IP) and the null-vs-empty-string convention for the four optional fields, but it adds nothing about tag format, note length, or owner syntax.

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?

States a specific verb (assign) and resource (nickname, owner, tags, notes in the local registry), and the parenthetical 'nothing changes on the router' cleanly separates it from router-mutating siblings like set_guest_wifi or reboot_router. It does not name a specific sibling to prefer or avoid, so it falls just short of a 5.

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?

Usage is implied rather than stated: the tool is for local metadata annotation. The description does explain the important field-editing convention ('pass "" to clear; omit to leave it alone'), which is real guidance, but it gives no when-not-to-use condition or alternative tool.

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