iaas_get_fabric_image

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is clear. The description adds useful domain context about what a fabric image is, but it does not describe response behavior or authorization requirements.

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 short and front-loads the main operation. The initial 'Get fabric image' restates the tool name, and the trailing GET endpoint duplicates the annotation title, but the remaining content is useful and efficient.

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-by-ID tool with full schema descriptions and annotations, the definition is largely complete. It explains the resource domain well enough to call the tool correctly, and no output schema exists to require return-value documentation.

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 id, select, and apiVersion. The description only reinforces that retrieval requires a given id, adding no further parameter semantics. 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 states a specific verb and resource: retrieving a single enumerated fabric image by ID. It also explains what fabric images are. It does not explicitly contrast with the plural sibling iaas_get_fabric_images, but 'with a given id' implies single-item retrieval.

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 description gives context that fabric images are region-specific and can be used in image mappings. However, it does not explicitly say when to use this tool versus iaas_get_fabric_images or iaas_get_images, nor does it state prerequisites such as knowing the image ID.

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