snapshot_list

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

No annotations are provided, so the description must fully disclose behavior. It mentions the results are ordered newest first, but does not mention side effects, access requirements, or error conditions (e.g., if the directory doesn't exist). The output schema exists, which explains return values, so some behavioral detail is deferred.

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 extremely concise: two sentences that state the function and a usage scenario. No unnecessary words or details.

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 simplicity of the tool (one parameter, has output schema), the description covers the essential purpose and a realistic use case. It does not explain what constitutes a snapshot or the output format, but the output schema likely handles that. Missing some edge case guidance but adequate for most scenarios.

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 only parameter 'out_dir' has no description in the schema (0% coverage). The description only says 'in a directory' without elaborating on the parameter's meaning, format, or constraints. This fails to compensate for the schema's lack of documentation.

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?

Description clearly states 'List snapshots in a directory, newest first.' This is a specific verb (list) and resource (snapshots) with ordering and scope. It distinguishes itself from siblings like snapshot_capture or snapshot_diff by focusing on listing.

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 a concrete use case: 'Useful when you've been taking periodic snapshots and need to find "the one from before yesterday's deploy."' This implies when to use it, but does not explicitly state when not to use it or compare to alternatives like snapshot_diff for comparing snapshots.

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