list_file_snapshots

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation ('List') but does not disclose potential behaviors such as pagination, sorting, permission requirements, rate limits, or what exactly is returned (metadata vs. content). The phrase 'all snapshots' adds some scope clarity but not behavioral detail.

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 a single, concise sentence that directly states the tool's purpose. It is appropriately sized, front-loaded with the verb, and contains no extraneous information.

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?

The tool is simple with one parameter and no output schema, and the description adequately covers the primary purpose. However, it lacks behavioral context and usage guidance, which would help an agent confidently invoke it. The sibling tools provide some context about snapshots, but the description itself is minimal.

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 input schema already provides a description for fileId ('File ID to get snapshots for'), achieving 100% schema coverage. The tool description adds no additional meaning about parameters beyond the schema, so the baseline score of 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 tool lists all snapshots (versions) of a file, using the specific verb 'list' and identifying the resource as 'snapshots of a file'. It distinguishes itself from sibling snapshot tools like create_file_snapshot, delete_file_snapshot, and restore_file_snapshot by focusing on the read operation.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that this is the appropriate tool for viewing version history, nor does it exclude scenarios better served by other tools like restore_file_snapshot or get_file. The description only states the function, leaving usage context entirely implied.

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