list_images

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

Given the lack of annotations, the description should disclose behavioral traits such as pagination, output format, or authentication. It only states 'list all available', which is already implied by the tool name, and does not elaborate on the behavior of the optional filters or any thresholds.

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, efficient sentence with no redundant content. However, it could be slightly more structured to include key behavioral details without becoming verbose.

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 read-only list tool with no annotations and no output schema, the description is too minimal. It lacks information about return values, pagination, and when filters might yield empty results (which is hinted in the schema but not in the description).

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 the baseline is 3. The tool description does not add additional meaning beyond what is already in the schema's parameter descriptions (e.g., depth limits, filter format).

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 'List all available images (OS templates) in IONOS CLOUD', clearly identifying the verb (List), resource (images/OS templates), and scope (all available). This distinguishes it from sibling tools like 'list_templates' by clarifying that images are OS templates.

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 like 'list_templates' or 'get_template'. There is no mention of prerequisites, filtering behavior, or context for usage.

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