session_start

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

With no annotations, the description comprehensively covers behavior: creates fresh empty session, ensures no data leakage, returns new session ID, and guarantees isolation. No contradictions.

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?

Well-structured with sections and steps, but somewhat verbose. Every part adds value, though could be slightly more concise.

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 no output schema, description adequately explains what is returned (session ID with timestamp-prefixed UUID). It integrates with sibling tools and covers all necessary context for initialization.

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?

No parameters, but description adds meaning beyond schema by explaining the session concept and its role. According to guidelines, baseline is 4 for zero params, and this is appropriately descriptive.

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 'Start a new memory session' with a specific verb and resource. It distinguishes from sibling tools by emphasizing this is the initialization step for a new conversation.

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?

Provides explicit workflow instructions: call first, then memory_retrieve, then memory_store. It also emphasizes one-time usage per conversation and warns against alternatives.

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