session_delete

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

With no annotations present, the description carries the full burden of disclosing destructive behavior. It clearly states the action is permanent and that all recorded events will be deleted, which is meaningful for a dangerous operation. However, it does not mention effects on currently active sessions or error handling.

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, direct sentence with no redundant information. The key facts (permanence, target, and cascade effect) are front-loaded and every word contributes meaning.

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 description covers the core destructive behavior but omits any mention of return values, error behavior, or what happens if the session is currently recording. Given the lack of an output schema and annotations, more contextual detail would be helpful for safe and correct use.

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 schema has 0% description coverage and only defines session_id as an integer. The description implies that the parameter identifies the session to delete, but it does not explicitly explain its role. While the tool name and parameter name make the semantics inferable, the description adds minimal value beyond the schema.

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) and the specific resource scope (a session and all its recorded events). This distinguishes it from sibling session tools like session_end, session_list, or session_search.

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?

No guidance is provided on when to use this tool versus alternatives such as session_end, nor are prerequisites, consequences for active sessions, or post-conditions described. The description lacks any usage context.

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