destroy_session

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

Despite no annotations, the description discloses that the tool destroys the session and releases resources, and that sessions become irreversibly terminal. This adequately informs the agent of the destructive nature and cleanup behavior.

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 sentences, front-loaded with the action and immediate usage guidance. Every sentence adds value with no redundant information.

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 simple signature and lack of output schema, the description covers the essential aspects: purpose, when to call, and terminal state constraint. Missing details about return values or errors are acceptable for this context.

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 single parameter 'session_id' is self-explanatory, but the description adds no additional meaning beyond the schema. With 0% schema description coverage, the description should compensate by explaining valid session IDs or format, but it does not.

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 ('Destroy') and clearly identifies the resource ('simulation session' and 'release all resources'). It distinguishes well from sibling tools like commit_session and discard_session by explicitly mentioning the destruction action.

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?

Provides clear usage context: 'Call this after commit or discard to clean up' and warns that sessions in terminal states cannot be reused. While it lacks explicit exclusion of other scenarios, it gives sufficient guidance for correct invocation.

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