end_session_summary

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

No annotations provided. The description indicates creation and proposing memories but does not disclose side effects, whether it modifies existing data, or if the proposal requires confirmation. The behavioral footprint is partially unclear.

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 sentences, concise and front-loaded with purpose. No wasted words, though could be slightly more structured with explicit parameter mapping.

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?

Moderate complexity (5 params, 3 required, no output schema). Description covers main intent but lacks details on return value and the meaning of 'proposes durable memories.' Adequate but not fully complete.

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%, so the description must add meaning. It mentions what_changed, what_worked, what_failed but omits files and summary_title. It adds some context but is incomplete for all parameters.

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 records what changed, worked, and failed at session end, creating a summary and proposing memories. It distinguishes from sibling remember_* tools which focus on individual items, but does not explicitly differentiate.

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 specifies 'at the end of a work session,' providing clear context. However, it does not explicitly exclude use during a session or guide when to use this versus sibling tools like remember_decision.

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