session_recap

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the output token range, structured vs. raw nature, and the specific knowledge categories returned (files touched, decisions made, next steps, conventions). It does not explicitly state read-only behavior or error behavior, but the 'Get a synthesized recap' framing makes the non-destructive intent clear.

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 well-structured and front-loaded with the core purpose, then provides trigger conditions, return contents, follow-up routing, and parameter explanations. Every section earns its place; the formatting with bullets makes the usage guidance easy for an agent to parse and act on.

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?

For a simple two-optional-parameter tool with no output schema, the description is complete: it covers when to call, what it returns, what it does not return, how to follow up for deeper detail, and the meaning of both parameters. Nothing essential is missing for an agent to select and invoke the tool correctly.

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 description coverage is 0%, so the description must compensate for parameter meaning. It does: session_id is explained as an optional specific session with a default of recent sessions, and limit is explained as max recent sessions with default 3. This adds practical semantics beyond the raw schema titles and defaults.

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 'Get a synthesized recap of recent session knowledge', specifying the resource (recent sessions), the output form (structured, ~150-250 tokens), and explicitly distinguishes itself from raw outputs. It also routes to topic_context for deeper detail, helping differentiate it from that sibling.

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 'AUTOMATIC TRIGGERS' with concrete scenarios for when to call this tool first, including starting work, answering 'what have we been working on?', and wanting files/decisions/next steps. It also names topic_context as the follow-up alternative when more detail on a topic is needed, giving clear when-to-use and when-to-use-as-alternative guidance.

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