list_sessions

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

No annotations are provided, so the description must carry the behavioral burden. It states the tool is read-only, does not trigger model initialization, returns results sorted by last update, and raises ValueError for invalid limit values. This provides clear behavioral expectations beyond the schema, though additional details like pagination or response structure are already given in Returns.

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 concise and well-structured (Args, Returns, Raises). Every sentence serves a purpose—purpose, behavior, parameter guidance, error info. 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 the tool's simplicity (1 parameter, no required params, output schema in description), the description fully covers purpose, usage, constraints, error handling, and return format. Sufficient for an agent to invoke it 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?

With schema description coverage at 0%, the description adds meaning by explaining the 'limit' parameter: maximum number to return (default 20, must be >=1) and that ValueError is raised if limit is <1 or >200. This covers constraints and error handling.

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 'セッション一覧を返す（直近更新順）', meaning 'Returns list of sessions (most recently updated first)'. It specifies the verb (返す/returns), resource (セッション一覧/list of sessions), and sorting order, distinguishing it from sibling tools like save_memory, search_memory, and delete_memory.

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 that this is a read-only operation that does not cause model initialization, guiding when to use it for safe, lightweight queries. However, it does not explicitly mention when not to use it or compare with siblings, though the context signals indicate it is distinct.

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