List snapshots

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds behavioral details beyond these: 'newest first', 'local files only', and that snapshots are created with litescope_snapshot requiring --allow-writes. No contradiction with 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?

The description is two sentences and a short phrase, front-loaded with the action and result. Every sentence adds value: first states function and ordering, second provides usage guidance and constraint. No wasted 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 (one parameter, known output schema), the description covers purpose, usage, constraints, and behavioral traits. With output schema present, explanation of return values is not needed. It is complete for an agent to select and invoke 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?

Schema coverage is 100% with one parameter 'source' described as 'Local SQLite file path.' The description reinforces this by mentioning 'local SQLite database' and 'local files only' but does not add new semantic details beyond the schema. Baseline 3 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 verb 'list', the resource 'point-in-time snapshots (local backups)', and the scope 'for a local SQLite database, newest first'. It distinguishes from sibling tools by focusing on snapshots, which are unique among the listed siblings.

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 provides explicit usage context: 'Use this to find a snapshot to restore, or to confirm a database has a backup before a risky write.' It also mentions the creation tool (litescope_snapshot) and the requirement for --allow-writes, guiding when to use this tool vs. alternatives. It also states 'Read-only; local files only'.

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