Delete Browser Session

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

Annotations already state destructiveHint=true and idempotentHint=true, but the description adds context the annotations cannot: the blast radius is limited to a .json file in this server's session directory, and the underlying instance UI session is NOT terminated (it expires at idle timeout). That scoping is exactly the kind of information an agent needs before invoking a destructive tool.

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?

Three short sentences, front-loaded with the action and its origin, then blast radius, then the non-obvious lifetime note. Nothing is redundant or padding.

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 no output schema, the description covers scope, provenance of the path, and the important semantic that only the file (not the UI session) is removed. It could still mention behavior on a stale or invalid path, but the essential calling information is present.

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 parameter description already says 'The path create_browser_session returned.' The description reinforces the source of the path and constrains it to a .json file under the session directory, but adds no format or error-handling detail beyond that.

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?

States a specific verb and resource ('Delete a browser session file') and ties it directly to the sibling that produces the artifact ('that create_browser_session wrote'). This makes it trivially distinguishable from create_browser_session and unrelated delete_* siblings.

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?

Gives a clear timing condition ('once the browser work is done') and implicitly routes the agent to create_browser_session for the counterpart path. It stops short of naming exclusions or failure cases (e.g., what to do if the session is still active), so it is not a full when/when-not statement.

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