session_start

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

No annotations are provided, so the description must fully disclose behavior. It lists the many returned items and mentions saving a session start marker and reconstructing from git log. However, it does not discuss side effects like potential state resets, performance impact of the large return, or error handling. Adequate but not comprehensive.

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 concise and front-loaded with the key purpose. It lists return items in a readable format without unnecessary verbosity. Minor improvements could be made with bullet points, but it is already efficient.

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 the tool's complexity (multiple return items, side effects, 5 parameters, no output schema), the description covers the main functionality and return values. However, it lacks details on expected behavior for invalid inputs (e.g., missing instance_id) or failure modes. Adequate for core use but leaves some gaps.

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?

All 5 parameters have descriptions in the schema (100% coverage). The description adds valuable context beyond the schema, such as how 'focus' surfaces relevant lessons, 'author' enables team telepathy, and 'workspace_path' triggers git log reconstruction. This enhances understanding.

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 it is a 'Single-call session briefing' to be called at session start, explicitly distinguishing it from sibling tools like smart_recall and recall_best_solution. The verb 'call' and resource 'session start' are specific and unambiguous.

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 instructs when to call ('at the START of every session') and what to use instead ('INSTEAD of multiple separate smart_recall/recall_best_solution calls'). It also mentions the marker for session_end. While clear, it could include guidance on when not to use this tool (e.g., for single queries).

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