openstack_list_images

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

With no annotations, the description must disclose behavioral traits, but it only says 'List available images.' It does not state whether the operation is read-only, whether pagination or filtering is supported, what authentication is required, or any side effects. This is a significant gap for a tool with no annotation fallback.

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 concisely states the tool's purpose. It is not verbose, and every word is meaningful. However, it is extremely terse, which limits its helpfulness but does not warrant a lower score for conciseness.

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?

The tool has a required device_id parameter that is not explained in the context of listing images, and there is no output schema or annotation to clarify expectations. The description is too sparse to give an agent a complete understanding of when and how to use this tool, especially given the large sibling context.

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 schema already documents device_id as 'OpenStack device ID.' The description adds no additional meaning about the parameter, such as why it is needed or how it affects the results. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 available images in OpenStack (Glance), which is a specific verb (list) and resource (images) that distinguishes it from sibling tools like openstack_list_servers or openstack_list_flavors. However, it does not clarify the role of the required device_id parameter, leaving some ambiguity about whether images are scoped to a device.

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 such as openstack_list_servers or openstack_list_flavors. The description does not mention prerequisites, exclusions, or typical use cases, so an agent has no help in selecting this tool over similar list tools.

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