tailscale_delete_oauth_app

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

The description goes well beyond the annotations by explaining concrete consequences: client secret stops working immediately, integrations lose device-enrollment paths, and already-enrolled devices remain in the tailnet. This gives the agent a clear mental model of the destructive side effects, matching and enriching the destructiveHint annotation.

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 three compact sentences with no filler. It front-loads the action, then explains the irreversibility and side effects, then provides the prerequisite lookup step. Every sentence earns its place.

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 single-parameter destructive tool with annotations already marking destructive and read-only hints, the description is complete: it explains what happens on deletion, what survives deletion, and how to obtain the required appId. No output schema is present, but the description covers enough for an agent to invoke the tool 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%, and the appId parameter is already described as 'The OAuth app ID to delete (see tailscale_list_oauth_apps)'. The description repeats the reference to list_oauth_apps but adds no new parameter-level meaning, so the baseline score of 3 applies.

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?

Description states a specific action ('Delete an OAuth App') on a specific resource, and the alpha qualifier adds useful context. The resource is distinct from sibling delete tools like tailscale_delete_key and tailscale_delete_device, so an agent can immediately understand the tool's scope.

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 clearly advises using tailscale_list_oauth_apps to find the id, which is actionable guidance for invoking the tool. It also warns that the operation is irreversible and breaks integrations, giving strong situational context, though it does not explicitly state when not to use it or compare it with alternative OAuth app tools.

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