Metis — Session Bootstrap

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

With no annotations, the description takes full responsibility for behavioral disclosure. It explains the conditional logic (check for active session, resume or create), the return of last 5 events or seeding from memory, and the required client parameter. It does not mention side effects like database writes or error handling, but the disclosed behavior is sufficient for most use cases.

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, using a clear header and bullet-like structure. Every sentence adds value: purpose, conditional logic, and parameter. No wasted words.

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 presence of an output schema (not shown but indicated), the description need not detail return values, but it still mentions returning last 5 events or seeding context. It covers the core behavior well, though it could mention error scenarios or prerequisites like a valid computer identifier.

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 only parameter 'client' has a default in the schema but no description or enum. The description adds explicit allowed values ('code', 'chat', 'cowork', 'dashboard'), which is critical for correct invocation. This significantly adds meaning beyond the schema, especially with 0% schema coverage.

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 as 'Find or create a session for the current computer.' It uses a specific verb ('find or create') and resource ('session'), and distinguishes itself among siblings by being the only bootstrap tool. The detailed conditional logic (resume vs create) adds further clarity.

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 usage as a first step ('Stage 1') but does not explicitly state when to use or not use this tool, nor does it compare to alternatives. While the context suggests it's a prerequisite, the lack of explicit usage guidance lowers the score.

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