memo_session_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds 'Read-only' and mentions the purpose of finding session data for capture/inspection, providing behavioral context beyond the annotations.

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?

Three sentences: first declares the action, second explains use case and output fields, third explains parameters. No wasted words, front-loaded with key information.

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?

With an output schema present (not shown), the description need not detail return values. It covers the tool's purpose, read-only nature, output fields (session ids, transcript paths, project context), and parameter usage. For a list tool with good annotations and schema, this is 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% with detailed descriptions for both parameters (limit: 'sorted by most recently updated first (no clamp)'; project: 'Exact project-name filter…'). The main description only briefly mentions 'project narrows results and limit caps the number of sessions returned', adding minimal extra meaning beyond the schema.

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 starts with 'List tracked memo sessions', a clear verb+resource. It distinguishes from sibling 'memo_session_get' (single session) and other list tools like 'memo_list' (memos vs sessions). It also specifies what the list contains: session ids, transcript paths, and project context.

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 states it is read-only and used for finding recent sessions. It explains how to narrow results with 'project' and cap with 'limit'. It does not explicitly mention alternatives or when not to use, but provides clear context.

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