session_close

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

With no annotations provided, the description fully discloses behavioral traits: 7-day retention, automatic promotion of up to 5 soon-expiring memories with a 48h alert window, and that promote failures never fail the close. This adds significant transparency.

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 three sentences, front-loads the main purpose, then efficiently covers side effects and content guidelines. No wasted 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?

Given the tool's complexity (6 params, no output schema), the description covers all essential aspects: what it does, when to use, side effects, and what to include. It's complete for agent decision-making.

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 description coverage is 83% (high), so baseline is 3. The description adds value by explaining the summary's content (accomplishments, pending items, context) and the promotion side effect, though parameter meanings are mostly covered by 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?

The description clearly states the tool saves a session close summary before ending a conversation, specifying the verb 'Save' and the resource 'session close summary'. It also distinguishes itself from siblings like session_boot by mentioning its role in context continuity and memory promotion.

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 explicitly says to use this tool 'before ending a conversation' and guides what to include in the summary. While it doesn't state when not to use it or list alternatives, the context is clear from the sibling names and description.

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