session_delete

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

The annotations already flag destructiveHint, and the description reinforces and extends that by stating that the profile directory itself is deleted from disk and that active/default sessions are not the target. This meaningfully describes the destructive effect without contradicting the annotations.

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?

The description is one compact sentence with no filler. It states the action, the resource, and an important qualifier efficiently.

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, it would help to state whether the session must be closed first or whether deletion is irreversible, beyond 'on disk.' The annotations and detailed parameter schema cover a fair amount, but the description stays minimal and leaves some preconditions to inference.

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 100% and the tool description itself adds little detail about the parameters. The description's 'not active/default' phrase hints at target selection, but the meaning of name, lease, and session is otherwise fully carried by the input schema, so the baseline of 3 applies.

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 uses a specific verb ('Delete') and a specific resource ('a session's profile dir on disk'), and clarifies that active/default sessions are not targeted. It does not explicitly differentiate from sibling tools like session_close or profile_delete, but the on-disk profile deletion semantics separate it clearly enough.

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 description gives a negative constraint ('not active/default') but provides no explicit guidance on when to use this tool versus session_close, profile_delete, or other session-management siblings. The 'session' parameter description contains usage advice, but that is parameter-level rather than tool-selection guidance.

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