iaas_get_fabric_images

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that the collection is region-scoped enumeration data, which is useful context, but says nothing about pagination behavior, result size, or what a filtered/empty result looks like — the areas the annotations do not cover.

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 core concept sentence earns its place, but the opening 'Get allfabric images' is a redundant restatement (with a typo) and the trailing 'Get all enumerated fabric images' plus raw endpoint path repeat the same information a third time. Padding dilutes an otherwise adequate definition.

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 parameterless read-only list operation with full schema coverage and no output schema, the description covers what the resource is. It still omits pagination expectations and result ordering/shape, which matter for a collection endpoint whose paging params the agent must use correctly.

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 all six parameters (top, skip, count, filter, select, apiVersion) are already documented in the schema. The description adds no extra semantics — notably it does not connect the 'specific region' wording to any parameter, leaving how region scoping is expressed unexplained. Baseline 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 names a specific verb+resource (get fabric images) and explains the domain concept — enumerated images from a specific region that feed image mappings. That is more than a name restatement. It does not, however, explicitly differentiate itself from close siblings like iaas_get_fabric_image (singular) or iaas_get_images, so it falls short of a 5.

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 phrase 'could be used in image mappings' implies the downstream purpose, but there is no explicit when-to-use statement, no prerequisite, and no named alternative. An agent must infer that this is the listing counterpart to iaas_get_fabric_image and distinct from iaas_get_images.

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