delete_session

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

The description notes the action is 'Irreversible' and enumerates the state that is deleted (test cases, results, suggestions, API keys). However, it does not discuss permission requirements, consequences, or any side effects beyond the listed items.

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 two sentences, each sentence adds value (action + scope, irreversibility). No extraneous 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 a simple tool with one parameter and no output schema, the description provides purpose and irreversibility but lacks parameter details and usage context, leaving gaps for effective 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?

The input schema has one required parameter (workspaceId) with no description. The tool description does not explain what workspaceId is, format, or how to obtain it. With 0% schema coverage, the description must compensate but fails to do so.

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 'Delete a workspace and all its state' and lists specific items (test cases, results, suggestions, API keys), which distinguishes it from sibling tools that do not have delete functionality.

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, no prerequisites, and no conditions under which deletion is appropriate.

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