delete_session

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

Discloses destructive behavior (cascade delete) and irreversibility. With no annotations, this is sufficient for a delete tool, though permissions or rate limits are not mentioned.

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 sentences, no redundancy, crucial warning front-loaded. Every sentence adds value.

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 simple delete operation, the description adequately covers behavior and caution. Output schema exists, so missing return details are acceptable.

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 does not explain individual parameters beyond the tool's purpose. Schema coverage is 50% (only session_id described), and actor_context is entirely undocumented in both schema and description.

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?

Clearly states 'Delete a session and all its errors and solutions.' This distinguishes it from siblings like close_session (probably non-destructive closure) and delete_old_sessions (bulk deletion).

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?

Includes a warning about cascade deletion and irreversibility, which indicates when to use (permanent removal) and when to avoid (if reversibility needed). Could explicitly mention alternatives like close_session.

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