Metis · Memory Curator — Save Session Summary

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

No annotations are provided, so the description should disclose behavior. It states 'save to persistent memory' and mentions return value, but lacks details on mutation effects (e.g., does it overwrite existing summaries?), permissions needed, or error handling. The description provides basic transparency but could be more comprehensive.

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 concise and well-structured: one paragraph for purpose, then bullet lists for arguments and return value. Every sentence adds value, no fluff. Front-loaded with the primary purpose.

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 simple save operation with 4 parameters (1 required) and no output schema, the description covers purpose, parameters, return format, and usage timing. It could be more complete by describing behavior on duplicate session_id or storage limits, but overall it's adequate.

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 0%, so the description is the sole source for parameter documentation. It explains each parameter's purpose, required status, format (2-5 sentences for summary, list of tags for key_topics, etc.), and optional nature. This adds significant value beyond the raw 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's purpose: saving a session summary to persistent memory for cross-session continuity. It uses specific verbs ('Save a summary') and directly distinguishes itself from sibling tool 'search_session_memory' (retrieval vs. storage).

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 use the tool: 'Call this at the end of any substantive session.' It also mentions future retrieval via search_session_memory, providing clear context for usage without describing when not to use it in detail.

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