Rename device

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds the reset-to-OS-hostname behavior and the empty-string convention, which is beyond the annotations. It doesn't mention permissions or side effects, but the idempotent and non-destructive hints cover the main safety profile.

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 sentence that states the primary action and the reset alternative. It is front-loaded with the main verb and resource, and every word earns its place. No fluff.

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?

For a simple two-parameter tool with a rich schema and clear annotations, the description is nearly complete. It explains the reset behavior, which is the main non-obvious aspect. It doesn't describe the return value, but there is no output schema and the tool is a simple rename operation, so that is acceptable.

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 100%, so the schema already documents both parameters well. The description adds the reset behavior tied to the name parameter, which complements the schema. It doesn't add much beyond the schema, but the schema is already rich, so a baseline of 3-4 is appropriate; the reset context gives it a 4.

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 the name of a device in the tailnet') and the resource (device in the tailnet), and also covers the reset behavior. It distinguishes itself from sibling tools like tailscale_get_device or tailscale_delete_device by focusing specifically on renaming.

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 implies when to use this tool: when you need to set or reset a device's name. It doesn't explicitly state when not to use it or name alternatives, but the context of renaming is clear. The schema adds guidance on the name format, which helps usage.

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