repl_delete_session

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds value by specifying 'all its data' as the deletion scope. However, it does not disclose other behavioral traits like irreversibility or any prerequisites, which would be useful for a destructive operation.

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 extremely concise, comprising just two short sentences with no redundant information. It is front-loaded with the core action and includes a brief return-value note, every word earning its place.

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 destructive tool with one parameter, the description adequately states what it does and the return type, while annotations cover the safety profile. However, it lacks usage guidance and any warning about consequences, making it minimally sufficient but not complete.

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 0% per the context signal, and the tool description does not mention the session_id parameter at all. Although the param name is self-explanatory given the tool name, the description fails to compensate for the low coverage, so the agent must rely on the schema's minimal 'Target session ID' 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?

The description uses a specific verb 'delete' with a clear resource 'session' and scope 'all its data', effectively distinguishing it from sibling tools like repl_delete_variable and repl_clear_namespace. The purpose is unambiguous and directly actionable.

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 provides no guidance on when to use this tool versus alternatives such as repl_clear_namespace or repl_delete_variable. There are no exclusions, prerequisites, or contextual recommendations, leaving the agent to infer usage solely from the name.

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