list_cluster_snapshots

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

With no annotations supplied, the description carries the full behavioral burden and falls short: it does not state that this is a read-only operation, whether results are paginated or ordered, or what authorization is required. The word 'frozen' hints at immutability of the snapshots but is never explained.

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?

A single front-loaded sentence with zero padding. It is tight, though the brevity comes at the cost of any usage or behavioral detail.

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?

This is a low-complexity list tool with safe optional parameters and no output schema, so not much prose is needed. Still, the description omits result ordering, pagination expectations, and the meaning of 'frozen', leaving the agent to learn the return shape by calling 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?

Schema description coverage is 100%, including an enum for target_type, so the schema fully documents limit, offset, and the type filter. The description adds no additional parameter meaning, which is the expected baseline when the schema does the work.

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 pairs a clear verb ('List') with a specific resource ('frozen archetype cluster snapshots'), which implicitly separates it from create_cluster_snapshot and get_cluster_snapshot. It does not, however, explain what an 'archetype cluster snapshot' actually is or how it relates to the sibling list_cluster_reports.

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 call this versus get_cluster_snapshot, list_cluster_reports, or create_cluster_snapshot, and no mention of paginating through results. The agent must infer all usage conditions from the tool name alone.

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