snapshots_list

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

The description adds no behavioral details beyond the basic listing action. It does not mention pagination, result ordering, or behavior when project_id is null. Annotations are absent, so the description carries full burden but fails to provide transparency.

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 at four words. It could benefit from slightly more detail about parameters without becoming verbose, but it is efficient and well-structured for a simple list operation.

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 has two optional parameters and an output schema, the description is incomplete. It fails to explain the effect of null project_id (likely listing snapshots from all projects) or the limit parameter for pagination. The output schema exists but the description does not leverage it.

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 has two parameters (project_id, limit) with no schema descriptions, and the tool description does not explain their meaning, default values, or how they affect the listing. The parameter semantics are entirely undocumented.

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 snapshots of a project, using a specific verb and resource. It implicitly distinguishes from sibling tools like snapshot_create, snapshot_delete, and snapshot_restore, but does not explicitly differentiate.

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 guidance is provided on when to use this tool versus alternatives. There are no sibling list-snapshot tools, but the description should specify context such as required permissions or typical usage scenarios.

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