m9k_delete_session

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds specific behavioral context: removes chunks and search data, preserves the JSONL file. This provides value beyond annotations, though it could mention side effects like cascade deletions.

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?

Two-sentence description that is efficient and front-loaded. First sentence states main action, second adds critical exception. No unnecessary words.

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 delete operation with one required parameter and no output schema, the description covers the action, what is removed, and what is not removed. Lacks information about return value or error conditions, but acceptable given context.

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?

Only one parameter (sessionId) with schema description 'The session ID to delete'. Schema coverage is 100%, and the description adds no additional meaning beyond the schema. Baseline score 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?

States it deletes a session from the index, removing chunks and search data, and explicitly notes it does not delete the source file. Verb 'delete' clearly indicates the action, and resource 'session' is specific. Distinguishes from siblings by clarifying the scope of deletion and what is preserved.

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 when to use (to remove session data while keeping the source file) but does not explicitly compare with alternative tools like m9k_forget or m9k_restart. No guidance on when not to use or prerequisites.

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