Outline a past conversation

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

No annotations are provided, so the description carries full burden. It states 'Very cheap even for huge sessions' indicating efficiency and non-destructiveness. It describes output as a 'numbered list of user prompts.' It could add details like output format exactness, but it's fairly transparent about behavior.

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 three sentences, front-loaded with the core purpose and key features. Each sentence adds essential information: output, efficiency/use case, and identification method with sibling reference. No unnecessary 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 no output schema, the description explains the return value: 'numbered list of the user's prompts, one line each.' It covers identification and use cases. It could mention error scenarios or limitations, but for a simple tool it is sufficiently 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 baseline is 3. The description adds value by explaining how parameters relate to usage: 'Identify the session by id or free-text query' and linking to load_session. This provides context beyond the schema descriptions.

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 action: 'Get a quick MAP of a past Claude Code conversation: the numbered list of the user's prompts, one line each.' It uses specific verb and resource and distinguishes from siblings by noting it provides outlines and turn numbers for use with load_session.

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 indicates when to use: 'to see what a session covered, or to find which turn numbers to then load with load_session's turns.' It also explains identification by id or query. It does not explicitly state when not to use, but the context implies alternatives like load_session for full content.

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