list_snapshots

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

The readOnlyHint annotation already discloses the read-only nature, and the description adds no further behavioral context such as pagination, result size limits, or the silent-empty-filter behavior (which is only in the schema). It does not contradict the annotation but offers minimal additional 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 a single, front-loaded sentence that directly states the action and scope. It contains no redundant words or filler, making it highly concise and easy to parse.

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?

For a simple read-only list tool with a well-documented schema and readOnlyHint, the description is adequate for selection and invocation. However, since there is no output schema, it could have mentioned the structure of the returned snapshot objects or any listing caveats; it does not, but overall the tool remains understandable and usable.

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 provides 100% coverage for both parameters (depth and filters), including nested object descriptions and a warning about filter typos. The description itself adds no parameter details, but the schema already carries the full semantic burden, so the baseline of 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 snapshots in the IONOS CLOUD account. It uses a specific verb ('list') and resource ('snapshots'), and the plural form distinguishes it from the singular get_snapshot sibling.

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 intended usage is implied by the name and description, but there is no explicit guidance on when to use this tool versus alternatives like get_snapshot, nor any mention of how filters or depth affect the listing. It does not provide exclusions or alternative recommendations.

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