revoke

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It clearly reveals the destructive scope: the description does not just say 'revoke' — it says the session and its local browser profile will be deleted. It could add detail about irreversibility or impact on other sessions, but the core destructive behavior is transparent.

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 precise sentence with no filler. The action verb and target resource are front-loaded, and every word contributes meaning. It could not be shortened further without losing key 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 one-parameter destructive tool, the description plus input and output schemas covers the basic operation and result. However, it does not mention where to obtain the session name (such as list_sessions) or provide any caution about the irreversible removal of the local profile, so it is minimally adequate but not fully complete.

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?

The input schema has 0% description coverage, so the description must compensate. It weakly implies that the session has a name, but it never explicitly states that the required 'name' parameter is the identifier of the session to delete or how to obtain a valid value. This is a meaningful gap for correct invocation.

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 uses a specific verb ('Delete') and names the exact resource ('a named session and its local browser profile'). It also distinguishes this tool from its siblings: none of sign_in, complete_sign_in, browse, or list_sessions implies deletion, so an agent can clearly see that revoke is the destructive session-removal operation.

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 intended use is implied: use this tool when you want to delete an existing named session and its local profile. However, the description does not explicitly state when this tool should or should not be used, nor does it point to alternatives like list_sessions for finding valid session names.

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