session_bootstrap

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

The description fully discloses the tool's behavior: it checks for an active session within a 2-hour window, resumes returning the last 5 events, or creates a new session with seeded context. No annotations are provided, so the description carries the full burden and meets it well.

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, front-loaded with the key purpose, and then structured into logical sections (behavioral logic, arguments). Every sentence adds value, and the Args section is clear and 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?

While the description covers the tool's behavior well, it lacks detail about the return value structure despite an output schema being present. It mentions returning 'the last 5 events' and 'seeded context', but does not specify the full response format, which could be needed for downstream use.

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?

The input schema only defines the 'client' parameter with a default and type. The description adds essential meaning: 'Which Claude client is calling ('code'|'chat'|'cowork'|'dashboard')', listing all valid values. Since schema coverage is 0%, this enrichment is critical.

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's purpose: 'Stage 1: Find or create a session for the current computer.' It specifies the action (find or create), the resource (session), and the scope (current computer), setting it apart from sibling tools like list_recent_sessions or get_working_memory.

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 is the first step ('Stage 1') and explains the conditional logic (resume vs. create), but it does not explicitly state when to avoid this tool or mention alternatives among the many session-related siblings, such as consolidate_session_memory or get_working_memory.

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