save_session_summary

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 discloses that the summary is stored persistently and is searchable, but does not mention whether it overwrites or appends, any authorization requirements, or error conditions. The behavioral context is adequate for a simple write tool but could be more explicit.

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 well-structured with a one-sentence purpose, a paragraph of context, and enumerated parameter explanations. Every sentence adds value, and it is appropriately concise.

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 4 parameters with 1 required, no output schema, and no nested objects, the description covers the tool's purpose, when to use it, how each parameter behaves, and the return value. It is complete for an agent to invoke correctly.

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 provides detailed, human-readable guidance for each parameter: summary should be 2–5 sentences, key_topics as short tags, decisions as key decisions, and session_id for grouping. This adds substantial meaning beyond the input schema, which only specifies types and defaults.

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 starts with clear verb+resource: 'Save a summary of the current session to persistent memory.' It further explains the purpose of cross-session continuity, which distinguishes it from siblings like search_session_memory or add_memory_entry.

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 states when to call: 'at the end of any substantive session.' It mentions that the summary is searchable via search_session_memory, providing relevant context, though it does not enumerate cases where the tool should not be used.

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