hcloud_list_images

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds little beyond noting it returns all objects and supports type filtering and sorting; it does not disclose pagination defaults, auto-pagination behavior, or the soft-cap, though those are documented in the schema.

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?

Two short sentences with no wasted words, front-loaded with the core action and scope. It is appropriately sized for a list tool whose parameters are fully described in the schema.

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 an 11-parameter list tool with no output schema, the description is adequate but thin. It covers the basic operation and mentions type/sort, but does not mention pagination behavior, return structure, or the breadth of available filters (name, status, architecture, labels, bound_to, include_deprecated).

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 coverage is 100%, so the schema fully documents all 11 parameters. The description reinforces type filtering and sorting, but adds no syntax or format details beyond what the schema already provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 a verb and resource: 'List Images' and 'Returns all Image objects.' It distinguishes the plural list operation from the singular hcloud_get_image sibling, but does not explicitly name or differentiate itself from hcloud_list_image_actions or other list endpoints.

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?

It mentions that you can select specific Image types and sort results, but gives no guidance on when to choose this tool over hcloud_get_image, hcloud_list_image_actions, or other list operations. No exclusions or alternatives are stated.

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