sb_list_snapshots

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

With no annotations provided, the description carries full burden to disclose behavioral traits. It does not mention that the operation is read-only, paginated (as implied by page/per_page parameters), or any auth requirements. The description is too minimal to inform about side effects or constraints.

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 with a single sentence, which improves readability. However, it is under-specified for a tool with three parameters and a list operation, missing essential details like pagination. It prioritizes brevity over being helpful.

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 that the tool has an output schema (not shown), the description need not detail return values. However, it still lacks context about pagination, ordering, or any filtering beyond the storage box ID. The description is insufficient for an agent to use the tool correctly without additional knowledge.

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 0% coverage (no schema descriptions) and the description does not explain any parameter. required storage_box_id is not described, nor are the optional page and per_page parameters. The description adds zero value beyond the schema itself, which is a major gap.

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 verb 'List' and resource 'snapshots of a Storage Box', making the tool's purpose immediately clear. It distinguishes from siblings like sb_create_snapshot, sb_delete_snapshot, and sb_get_snapshot, but does not differentiate from sb_list_storage_boxes or other list tools.

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. For example, it does not mention that sb_get_snapshot is for individual snapshots, or that sb_list_storage_boxes is needed first to get box IDs. The description offers no decision framework.

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