tailscale_device_expire

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

With no annotations, description fully conveys the irreversible consequence (lose connectivity, must re-auth), the fact the device stays in tailnet, and the confirm requirement. No contradictions.

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?

Three concise sentences, front-loaded with action, then consequence, then constraint. 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?

For a simple mutation with 2 params and no output schema, description covers purpose, effect, and confirmation. Missing error handling or return info, but 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?

Schema coverage is 100%, and the description reinforces 'confirm: true' but adds no new meaning beyond the schema. 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?

Clearly states 'Expire a device's key' with specific verb and resource. Describes effect (force re-auth, lose connectivity) and distinguishes from siblings like delete or authorize.

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?

Implicitly indicates when to use (force re-authentication) but does not explicitly contrast with alternatives like tailscale_device_authorize or tailscale_device_delete. Provides context for the one-directional nature.

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