session_delete

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

Annotations already declare destructiveHint=true, but the description adds substantial context: it deletes encrypted login data, is irreversible, requires re-login, and breaks references from monitors/requests. This goes well beyond the annotation and fully discloses the impact.

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 sentences, each earning its place: the action, the irreversible consequence with impact, and the id source. It is front-loaded and contains no redundant wording.

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 destructive one-parameter tool with annotations and an output schema, the description covers the essential warnings, the impact on other entities, and how to obtain the id. Nothing needed for correct invocation is missing.

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 already describes the id parameter as 'The session ID to delete (from session_list).' The description repeats the source of the id without adding new details about format or constraints. With 100% schema coverage, the baseline of 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?

The description clearly states the action: 'Permanently delete a saved browser session and its encrypted login data.' It names the specific resource and the verb, and it distinguishes from siblings like session_list (which lists sessions) by specifying deletion. The scope is unambiguous.

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 explains the irreversible nature and the consequence that monitors/requests lose authenticated access, implying caution. It also directs the user to session_list for finding ids. However, it does not explicitly state when not to use the tool (e.g., if a session is needed later), but the destructive warning makes the intended usage clear.

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