mem_session

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It gives high-level instructions but does not communicate side effects, whether starting a session overwrites previous state, what summary/checkpoint persist, or any constraints on calling them. The phrase 'manage the active memory session' is too generic to expose meaningful behavior.

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 compact sentences with no filler. It front-loads the core purpose and then gives direct actionable usage guidance.

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?

The description covers only action=start and action=summary, completely ignoring the checkpoint action and without explaining session IDs, id fallback, or the relation to sibling tools. Given no annotations and no output schema, the agent is under-equipped to fully understand the session lifecycle.

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 schema already provides 100% parameter coverage, so the baseline is 3. The description adds useful extra meaning by tying action=start and action=summary to session lifecycle moments, which is absent from the schema descriptions.

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 identifies the resource as the active memory session and uses the verb 'manage', supported by specific action guidance ('start at session start', 'summary before ending'). It is reasonably distinct from sibling memory tools like mem_save and mem_recall, though 'manage' is slightly generic.

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 action=start and action=summary, giving clear lifecycle context. It does not explicitly mention when to avoid this tool or contrast it with sibling memory tools, but the provided usage timing is useful enough.

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