memo_list

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

With no annotations, the description must disclose behavioral traits. It mentions pagination and the channel defaulting, which are useful. However, it omits details on ordering, error behavior, permissions, or the exact structure of returned 'memo information', leaving some gaps for an agent.

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 two sentences, front-loading the core action and adding relevant detail without redundancy. Every sentence earns its place, and it is clearly structured.

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?

Without an output schema, the description should explain return values more thoroughly. It only vaguely says 'paginated results with memo information', leaving the agent to infer field names and pagination metadata. Given the tool's simplicity, this is a moderate gap, so a mid-range score is appropriate.

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 the baseline is 3. The description adds the channel fallback context (already in schema) but does not enrich parameter meanings beyond what the schema provides, such as clarifying skip/take compounding or result shape. It is adequate but not additive.

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 identifies the tool as retrieving a list of memos, scoped to a channel with a fallback to the active channel. It distinguishes itself from siblings (memo_create, memo_get, memo_search) by focusing on list retrieval and pagination, making the purpose unambiguous.

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 explains the channel fallback behavior, providing context on how to use the tool. However, it does not explicitly state when to use this tool over siblings like memo_get (for a single memo) or memo_search (for finding memos by criteria), leaving the decision purely inferential.

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