delete_session

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

No annotations are provided, so the description carries the full burden. It reveals the tool performs a 'soft-delete', which is a key behavioral trait not derivable from the schema or name. However, it omits other important details such as authentication requirements, idempotency, what happens to associated data, or if the deletion is reversible. The single behavioral tidbit is insufficient for safe invocation.

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 short sentence with no waste, but it is under-specified. Conciseness is good, but the structure could be improved by adding necessary details without becoming verbose. It earns a 3 for being trim yet missing critical 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 low complexity (one parameter, no output schema) and no annotations, the description should provide sufficient context for a safe delete operation. It mentions 'soft-delete' but lacks details on consequences, return value, or side effects. The description is incomplete for an agent to understand the full impact of the tool.

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?

With 0% schema description coverage, the description must compensate but only adds 'by slug' to identify the parameter's role. The slug's format, constraints, or examples are missing. While the basic meaning is clear, the lack of detail limits the agent's ability to construct valid inputs.

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 verb 'soft-delete' and the resource 'session', with the identifier 'slug'. This explicitly differentiates it from sibling tools like delete_solution or delete_story, which target different resources. The purpose is unambiguous.

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 implies that the tool is used when you need to delete a session, but it provides no explicit guidance on when to use it versus alternatives, nor any prerequisites or conditions. For a simple deletion tool, the implicit guidance is adequate but not proactive.

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