list_snapshots

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

No annotations provided, so the description carries the full burden. It accurately describes the read-only nature ('List'), the ordering, and the filter behavior. No side effects or additional constraints are needed for a simple list operation.

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?

Two concise sentences covering action, ordering, filter, and return content. No extraneous information; every phrase 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?

No output schema exists, so the description must indicate return content. It specifies 'snapshot metadata with an id', which is sufficient for an agent to understand what is returned. However, it could be more explicit about what metadata fields are included.

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 description coverage is 100% for the single 'project' parameter. The description essentially repeats the schema's wording ('optionally scoped to a project-path substring'), adding no new meaning beyond the schema.

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?

Clearly states the verb 'list', the resource 'snapshots', ordering ('newest first'), optional filter by project path, and the return type ('snapshot metadata with an id'). This distinguishes it from sibling tools like load_snapshot which loads a specific snapshot by id.

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?

Provides clear context for when to use the optional project filter and that an empty string means all projects. However, it does not explicitly state when not to use this tool or mention alternatives like load_snapshot for direct access.

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