Delete Session

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

With no annotations at all, the description carries the full behavioral burden for a destructive operation. It does not state that deletion is irreversible, whether related activities/messages are cascaded, or what permissions are required — all material facts for a delete 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?

A single front-loaded sentence with no filler; the verb, resource, and scoping condition all appear immediately.

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 tool with no annotations and no schema descriptions, the definition is too thin. It omits reversibility, cascade behavior, and prerequisites; the presence of an output schema excuses it only from describing return values.

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 schema contributes no parameter meaning. 'By ID' clarifies session_id loosely, but the required _meta parameter is entirely undocumented in both schema and description, leaving the agent without guidance on it.

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 (delete) and resource (session) plus a scoping condition (completed or terminated), so the agent knows it is not a general-purpose session remover. It does not explicitly name or distinguish itself from the closest sibling, clean_completed_sessions, which also targets finished sessions.

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 phrase 'completed or terminated' implies the precondition for use, which is real guidance about applicability. However, there is no explicit when-to-use vs. when-to-avoid statement and no mention of clean_completed_sessions as the bulk alternative, so the agent must infer the routing.

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