delete_session

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the confirm=true guard to prevent accidental deletion, which is useful, but it fails to state that deletion is permanent, irreversible, or any potential side effects—a critical omission for a destructive operation.

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 concise, front-loaded sentences with no filler. The action and safety requirement are stated efficiently, making every word purposeful.

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?

Given the tool's simplicity (2 params, no output schema), the description covers the core action and safety mechanism. However, it omits details about permanence/reversibility and return behavior, making it minimally adequate but not comprehensive.

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 description adds value by explaining that confirm=true is required to prevent accidental deletion, which goes beyond the schema's type/default. However, session_id is only referenced as 'by ID' and not elaborated; with 0% schema description coverage, this partial compensation is moderate.

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 specific verb 'Delete' and the resource 'saved session' with the method 'by ID'. It distinguishes itself from sibling tools like update_session and get_session, making the purpose 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 context of use is clear: when you need to delete a saved session. It doesn't explicitly mention alternatives or exclusions, but the delete intent is straightforward, so it provides clear context without unnecessary caveats.

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