revoke

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

With no annotations, the description carries full disclosure burden. It clearly states the destructive action (delete) and an important side effect: the local browser profile is also removed. This goes beyond the schema and gives the agent a concrete understanding of consequences.

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, front-loaded sentence with no filler. Every word contributes: 'Delete' states the action, and 'named session and its local browser profile' states the exact scope.

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 operation, the description covers the essential information: what is deleted and the side effect on the local profile. The presence of an output schema handles return-value expectations. It could mention irreversibility or how to obtain a valid name, but overall it is sufficiently 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?

Schema coverage is 0%, so the description must explain the parameter. The phrase 'a named session' makes clear that 'name' refers to the session identifier to be deleted, which is the essential semantic. A reference to list_sessions as a source of valid names would have made it more explicit, but the meaning is still unambiguous.

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 the specific verb 'Delete' and names the exact resource: a named session and its local browser profile. This clearly distinguishes it from sibling tools like browse, list_sessions, sign_in, and complete_sign_in, which serve different purposes.

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 implies usage for deleting/revoking a session, which is inferable from the verb and resource. However, it does not explicitly state when to choose this tool over alternatives, such as sign_in or list_sessions, nor does it mention prerequisites like needing an existing session.

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