tailscale_derp_map_set

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

With no annotations, the description must disclose all behavioral traits. It reveals the confirmation requirement and the ID range constraint, but lacks details on authorization needs, rate limits, error states, or what happens if confirm is false. It does not contradict any annotations since none are provided.

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 only three sentences, each serving a clear purpose: stating the action, noting the confirmation requirement, and specifying key constraints. It is front-loaded with the main verb and resource, with no unnecessary words.

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?

Despite the complexity of nested parameters, the description covers the most important aspects: confirmation, ID range, and default region behavior. It does not explain merge vs replace behavior or return values, but combined with the detailed schema, it is largely sufficient for a tool of this complexity.

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 coverage is 100%, but the description adds value by emphasizing that confirm must be true, recommending custom region IDs 900-999, and explaining the effect of omitDefaultRegions. This provides clarity beyond the schema's own descriptions, though the schema already covers the basics.

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 or update' and the resource 'custom DERP relay map in the tailnet's ACL policy', distinguishing it from sibling tools like tailscale_acl_set (which sets ACL rules) and tailscale_derp_map (which likely retrieves the map). The constraints on IDs and omitDefaultRegions further clarify its specific purpose.

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 mentions the requirement for confirm:true and notes that custom region IDs should be 900-999, and omitDefaultRegions replaces defaults. However, it does not explicitly state when to use this tool versus alternatives like tailscale_acl_set or when not to use it, leaving some ambiguity for the agent.

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