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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says a session is opened and an ID is returned, without explaining session lifecycle, TTL effects, whether opening is destructive or idempotent, or what happens to prior sessions.

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 a single, front-loaded sentence with no filler or repetition. It is concise and readable, though it is so sparse that it sacrifices useful contextual detail.

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 action is simple, the output schema exists, and there are no required parameters, so the description covers the core call. However, it lacks lifecycle context, such as how the returned session relates to other memory_session_* operations and whether the session needs to be closed or can be reused.

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 100%, and each parameter already has a clear meaning in the input schema, including TTL, repo tagging, GitHub tagging, agent override, and topic. The description adds no parameter-level detail, but because the schema is fully self-documenting, the baseline of 3 applies.

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 states a specific action ("Open"), a clear resource ("working-memory session"), and the return value ("session_id"). It is understandable on its own, but it does not explicitly differentiate from sibling tools like memory_session_ensure or memory_session_append.

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 gives no guidance on when to call this tool versus alternatives such as memory_session_ensure, memory_session_append, or memory_session_close. There are no conditions, prerequisites, or exclusions provided, so the agent must infer the appropriate usage context.

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