Session Delete

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

With no annotations at all, the description carries the full burden for a destructive operation, yet it doesn't say whether deletion is idempotent, what happens when the name doesn't exist (error vs. {"deleted":false}), or whether it affects a live browser session. The return example duplicates what the output schema already provides, so it adds little behavioral insight.

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?

Two short lines, verb and resource front-loaded, followed by a concrete call/response example. Nothing is padded or redundant beyond the example's marginal overlap with the output schema.

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?

The output schema covers the return shape and there's only one parameter, so the basics are handled. For a destructive tool with zero annotation coverage in a session-management suite, though, the missing guidance on failure modes, irreversibility, and interaction with warm_session/session_load leaves a real gap.

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 description coverage is 0%, so the description must compensate for the single parameter. It does partly: 'by name' tells the agent the argument is the session name, and the example shows the expected string form ('github-me'). It stops short of stating naming conventions or constraints on the name.

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 states a specific verb and resource ('Delete a saved session blob') with the lookup key ('by name'), so it's clear this operates on persisted session blobs. Sibling tools session_save, session_load, and session_list make the resource family obvious, but the description never names them to sharpen the distinction.

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?

Usage is only implied: an agent can infer this removes a stored session, but there's no statement of when to prefer it over session_load/cleanup_stale or what prerequisites exist (e.g. that a browser must not be using that session). The example illustrates a call but not a selection rule.

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