delete_session

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'Delete' without disclosing whether deletion is permanent, what happens to associated data, error handling, or authentication requirements. The word 'delete' implies destructiveness but adds no further behavioral context.

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 sentence, but it is under-specified and duplicates the tool name. It does not earn its place as it provides no additional information beyond the name. This is not meaningful conciseness but rather under-specification, similar to the 'Process' example.

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 one-parameter delete tool, the description plus schema allow basic invocation, but there is no information about return values, success/failure behavior, or side effects. Given no output schema or annotations, the description is incomplete and leaves the agent uncertain about what happens when the tool is invoked.

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 description does not address the session_id parameter, but the input schema provides 100% coverage with a description 'Session ID'. Therefore, the schema already documents the parameter, and the description adds no extra meaning beyond what the schema provides. The baseline of 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 'Delete a session' simply restates the tool name 'delete_session' with no additional specificity about scope, permanence, or effect. It does distinguish from sibling tools like create_session/get_session, but provides no value beyond the name itself, making it a tautology.

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?

No usage guidelines are provided. The description offers no context on when to use this tool versus other delete tools (e.g., delete_knowledge), no prerequisites, and no mention of alternatives. It simply states the action without any situational guidance.

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