Enregistrer un épisode

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 session history feeds future consolidation, which is valuable behavioral context. However, it does not mention return values, side effects, or any limitations (e.g., idempotency, rate limits), so transparency is incomplete.

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 two sentences, front-loaded with the main action and followed by a clear usage instruction. Every word contributes; no filler or 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?

For a simple add operation with no output schema and no annotations, the description gives the core purpose and timing. However, it omits explanation of the 'project' parameter and what happens after the call (e.g., return value). These are notable gaps for an agent that must invoke the tool 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?

Schema coverage is 67% (summary and provenance have descriptions, project does not). The description adds some context by labeling the content as 'résumé épisodique' and mentioning provenance, but it does not clarify the optional 'project' parameter, leaving a gap.

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 episode (episodic summary + provenance) and explicitly references the 'episode' concept, distinguishing it from sibling tools like memory_add. The verb 'Enregistre' and resource 'épisode de session' make the purpose unambiguous.

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 call at the end of a conversation, giving a clear context of when to use this tool. It does not explicitly name alternatives, but the context implies it is for episodic session summaries rather than general memory entries.

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