bricks_list_snapshots

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

The description discloses that the tool is a read-only list operation, but it does not explain what data is returned (e.g., snapshot IDs, timestamps), pagination behavior, or any limits. Without annotations, this is insufficient for an agent to understand the tool's full behavior.

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, well-structured sentence with no fluff. It immediately conveys the purpose and key property (sorted by most recent).

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 no output schema and no annotations, the description should compensate by detailing return values or usage patterns. It does not mention whether snapshot IDs are included, how to interpret the list, or any pagination. This leaves the agent underinformed for subsequent calls like bricks_restore_snapshot.

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 100% coverage with descriptions for all parameters. The tool description adds no additional meaning beyond reinforcing that snapshots are 'for a page'. 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 tool lists all available snapshots for a page, sorted by most recent first. It uses a specific verb ('list') and resource ('snapshots for a page'), differentiating from sibling tools like bricks_snapshot_page (create) and bricks_delete_snapshot (delete).

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 no guidance on when to use this tool versus alternatives, such as when to list snapshots vs. creating or restoring them. It does not mention prerequisites, expected context, or exclusion criteria.

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