memo_session_list

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that it is read-only and returns session ids, transcript paths, project context, but no additional behavioral traits beyond what annotations cover. Adequate but not enriched.

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 with clear front-loading: 'List tracked memo sessions.' Then purpose and parameter details. No fluff, every sentence adds value.

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?

Has output schema (not shown but signaled), so return values need not be detailed. Description mentions key return fields: session ids, transcript paths, project context. Parameters are explained. Annotations cover safety. Sufficient for a list tool.

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 0%, so description must compensate. Description explains both parameters: 'project narrows results' (filtering by project) and 'limit caps the number of sessions' (pagination). Adds meaning beyond schema defaults and types.

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?

Specific verb 'List' + resource 'tracked memo sessions'. Clearly distinguishes from sibling tools like memo_session_get (get a single session) and memo_start_session. Mentions purpose: find recent 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?

Explicitly states read-only nature and use case ('find recent session ids...'). Describes parameter effects: project narrows, limit caps. Does not explicitly exclude scenarios but context is clear. Sibling tool memo_session_get exists for single session retrieval, providing implicit alternative.

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