tailscale_key_delete

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

With no annotations, the description discloses that devices already authenticated with the key will not be affected, a key behavioral trait beyond the basic delete semantics, though additional details like permissions or error states are absent.

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 two sentences, front-loaded with the purpose, and contains no redundant 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?

For a simple two-parameter tool with no output schema, the description covers the essential behavioral context (effect on devices, confirmation requirement) and is sufficient for the agent to invoke correctly.

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%, so the description's addition that confirm must be true adds minimal new meaning beyond the schema's description; the keyId parameter is not elaborated further.

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 'Delete (revoke) an auth key', specifying the verb and resource, and distinguishes from sibling tools like tailscale_key_create and tailscale_key_list by focusing on the delete action.

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 explicitly mentions 'Requires confirm: true', guiding the agent on a necessary precondition, but does not discuss when not to use or provide explicit alternatives to other key operations.

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