delete_session_trees

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly states that the tool deletes all trees and thoughts for a session, clearly communicating the destructive scope. It does not mention irreversibility explicitly, but 'Delete all' conveys the destructive nature sufficiently for this simple 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?

The description is a single, focused sentence that front-loads the action and scope. There is no filler or repetition of schema details, making it easy to parse quickly.

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 one-parameter destructive tool with no output schema, the description adequately specifies what is deleted and for which session. It is slightly incomplete in that it does not warn about irreversibility or confirm cascading deletion of thoughts beyond the main phrase, but overall it is sufficient for correct invocation.

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 sessionId parameter is already described as 'The session ID to delete trees for'. The tool description adds little beyond that, so the schema carries the semantic weight; baseline 3 is appropriate.

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 ('Delete'), the resource ('all trees and thoughts'), and the scope ('associated with a specific session ID'). This distinguishes it from related tools like list_trees_by_session and delete_tree without requiring the reader to inspect schemas.

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 word 'for cleanup' implies the intended use case, but there is no explicit guidance on when to choose this over delete_tree or when not to use it. Sibling alternatives are not mentioned, so an agent must infer the usage from the name and description.

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