session_start

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

Despite no annotations, the description discloses key behaviors: session initialization, agent detection, loading of context, and the note about scars surfacing via recall(). It also explicitly instructs on handling the 'display' field in output. However, it does not mention side effects of the 'force' parameter on existing 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 very concise with two short paragraphs. The first paragraph states the core functionality, and the second provides crucial output handling instructions. Every sentence adds value, and there is 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?

The description covers initialization and output display instructions but lacks details on return structure beyond the display field, error conditions, or prerequisites. Given the complexity (7 params, no output schema), it is adequate but not 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 coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond the schema; it mentions loading context but does not map to specific parameters. The parameter descriptions in the schema are already clear.

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 initializes a session, detects the agent, and loads institutional context (last session, recent decisions, open threads). It uses specific verbs and resources, and the purpose is distinct from siblings like session_refresh or session_close.

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 implies this tool is used to start a session but provides no explicit guidance on when to use it versus alternatives like session_refresh. There is no mention of when-not to use or what prerequisites exist.

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