delete_memories_by_session

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

With no annotations, description carries full burden. It discloses deletion scope, irreversibility, and scope to configured owner. Lacks auth notification or rate limits, but irreversibility is well-stressed.

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?

Four sentences with no waste. Each sentence contributes: what is deleted, when to use, warning. Front-loaded with action.

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 single-parameter tool with no output schema, description covers purpose, usage, and behavioral caveats. Could mention return value or error handling, but overall sufficient.

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 parameter description is basic. Description adds meaning by linking session_id to deletion of all associated memories and scoping to owner, enhancing understanding beyond schema.

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?

Clearly states the verb 'delete', the resource 'every memory (singles, parent docs, child chunks, sha guards)', and the scope 'session_id' and 'owner'. Distinguishes from sibling 'delete_memory' by specifying bulk deletion per session.

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?

Provides explicit use cases: 'wrap up a finished project' or 'reset a polluted session'. Includes a strong warning to confirm session_id. Could improve by explicitly contrasting with single memory deletion.

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