web_session_delete

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It transparently lists consequences: closing the open window and erasing cookies and site data, which clearly conveys that this is a destructive operation. It could explicitly say 'irreversible', but 'deletes' and 'erases' are already strong signals.

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?

A single sentence with the action front-loaded and the side effects listed compactly after a colon. Every word contributes meaning, and there is no filler or repetition.

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 zero-parameter, destructive tool with no output schema, the description covers the core action and its immediate effects well. The only slight gap is that it does not specify which profile is deleted when multiple saved profiles exist, but the absence of parameters implies a context-determined or singleton target.

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 tool has zero parameters, so there is no parameter documentation burden on the description. The schema is trivially 100% covered, and the baseline for zero-parameter tools is appropriately high.

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 opens with a specific verb ('Deletes') and a specific resource ('SAVED web-automation login profile'). It also enumerates concrete effects, which makes it clearly distinct from siblings like web_session_close that only close an active session.

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 provides no guidance about when to choose this tool over related alternatives such as web_session_close or web_login, and it does not mention any prerequisites or exclusions. The destructive use case is implied but never framed as a choice point.

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