list_snapshots

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

With no annotations, the description must disclose behavioral traits. It only states 'list all snapshots', omitting details such as pagination behavior, rate limits, or whether the operation is read-only. The existence of parameters like 'depth' and 'filters' suggests control over output, but these are not explained behaviorally.

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 (one sentence) but lacks necessary detail. While front-loaded with the purpose, it is under-specified for a tool with parameters and no output schema. Conciseness does not compensate for missing 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?

Given no output schema and no annotations, the description should provide a complete understanding of the tool. It fails to describe what the response contains, how depth/filters work, or any limitations. The tool is part of a large family, but the description does not position it adequately.

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%, so baseline is 3. The description adds no additional meaning beyond the schema's own parameter descriptions. It does not provide examples or context for how 'depth' or 'filters' affect the listing.

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 explicitly states the tool's purpose: 'List all snapshots in your IONOS CLOUD account'. It uses a specific verb ('List') and resource ('snapshots'), clearly distinguishing from sibling tools like 'get_snapshot' (retrieves a single snapshot) and 'list_images' (different resource type).

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 is no mention of why one might use 'list_snapshots' instead of 'get_snapshot' or other listing tools. The description lacks context about typical use cases or prerequisites.

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