Set device IP

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the basic safety profile. The description adds no additional behavioral context (e.g., potential disconnection of the device, permission requirements, or side effects). It is consistent with annotations but doesn't enrich the agent's understanding beyond them.

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 a single concise sentence that immediately conveys the core action. There is no fluff or redundant wording, and it is front-loaded with the verb and resource.

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 simplicity of the tool (two required parameters, well-documented schema, no output schema), the description is minimally sufficient but lacks contextual details like the implications of changing an IP address or when this should be used. It doesn't mention any constraints or edge cases, but for a straightforward set operation it is adequate.

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 has 100% coverage with detailed descriptions for both parameters: deviceId explains the source and format (nodeId from tailscale_list_devices, not nodeKey), and ipv4 gives an example. The tool description itself adds no parameter-specific information, but the schema already handles semantics well, so a baseline 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 clearly states the action ('Set') and the resource ('Tailscale IPv4 address for a device'), which is specific and distinct from sibling tools like tailscale_set_device_routes or tailscale_set_device_tags. An agent can immediately understand what this tool does without ambiguity.

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 no guidance on when to use this tool versus alternatives. There are many sibling tools that modify devices (e.g., rename, expire, set routes), but no context is given about selecting this one over them. It simply states the action without any usage conditions or exclusions.

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