List saved sessions

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

No annotations are present, so the description carries the burden of transparency. It discloses 'newest first' ordering and lists the fields returned, which implicitly suggests a read-only operation, but it doesn't explicitly state that no side effects occur, require permissions, or handle empty lists. Some behavioral detail is provided, but not exhaustive.

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?

A single concise sentence captures the resource, the returned fields, and sorting order without any filler or redundancy. Every word earns its place, making it highly efficient and readable.

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?

For a simple zero-parameter listing tool with no output schema, the description is fully complete: it names the resource, enumerates the return values, and specifies ordering. There is no missing information that an agent would need to confidently invoke this 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?

The tool takes zero parameters, so schema coverage is trivially 100%. The description adds value by explaining what the returned list contains (name, save time, card count, deck names), which provides context beyond the empty schema. However, with no parameters, there is little to add, so the baseline of 4 is appropriate.

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 function: 'All saved kitchen-table sessions' with explicit mention of returned fields (name, save time, card count, deck names) and sort order ('newest first'). This distinguishes it from sibling tools like session_save and session_load, which have different purposes.

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?

No explicit when-to-use guidance is provided, but the listing behavior is implied by the verb 'List' and the resource 'saved sessions'. Sibling tools session_save and session_load exist, yet the description doesn't clarify when to use this tool over them, such as 'use session_load to load a specific session'.

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