Start Session

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool is an entry point but does not explain side effects (e.g., whether it creates a new session, overwrites existing, or returns a session ID). The description focuses on when to use rather than what the tool does internally.

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 a clear instruction ('[ENTRY — call FIRST, before acting]'), followed by usage guidance for mode. Every word serves a purpose with no 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?

Given 4 parameters (0 required) and no output schema, the description tells when to use and how to choose mode, but does not explain return behavior, what 'auto' project means, or how the session context behaves. This is adequate for a simple intent-detection scenario 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 description coverage is 75% (3 of 4 parameters described). The description adds value for the 'mode' parameter by explaining when to use 'lite' vs 'full', but does not add information for 'context' or 'verbose' beyond the schema. The 'project' parameter has no description in schema or description, leaving it unclear.

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 is an entry point for starting, loading, continuing, resuming, or opening memory for a project. It uses specific verbs like 'start' and 'load' and distinguishes from sibling tools like 'session_end' by emphasizing it is called first before acting.

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 use when the user asks to start/load/continue/resume/open memory. It provides mode guidance, recommending 'lite' for fresh conversations to pull memory on demand via alternatives like 'recall/memory_query/skill_recall', clearly indicating when to use this tool versus alternatives.

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