save_session_summary

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

Describes that the summary is stored to persistent memory and is searchable later. The return value is described as a dict with id and confirmation. Lacks explicit detail on overwrite behavior or limits, but adequate for the complexity.

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?

Very concise: one sentence for purpose, a paragraph for usage, structured Args section, and Returns. No redundancy.

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?

Covers all necessary aspects for a save operation: purpose, when to use, parameter meanings, return value. References retrieval counterpart. No gaps given the tool's simplicity.

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 coverage is 0%, but the description provides rich details for each parameter: required summary length, optional key_topics with examples, decisions with examples, and session_id with grouping behavior. Adds significant value beyond the 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 'save', the resource 'summary of current session', and the purpose 'cross-session continuity'. Distinguishes from siblings like 'save_session_event' and pairs with 'search_session_memory'.

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?

Explicitly says 'Call this at the end of any substantive session' and explains the benefit of cross-session continuity. Does not state when not to use, but the context is clear enough.

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