iaas_get_image_profile

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 fully covered elsewhere. The description adds nothing beyond restating the REST path — no note about 404 behavior for unknown IDs, permission requirements, or what an image profile contains.

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?

Very short, but the first two lines are near-duplicates of each other and of the title, and the OpenAPI path is repeated verbatim from the annotation title. It is front-loaded but partly wasteful rather than dense with information.

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 call with rich annotations and a fully documented schema, little is required, but the description still omits what a returned image profile represents and how it relates to images/image profiles listing. An agent can invoke it, but understands almost nothing about the resource.

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% and both parameters (`id` and `apiVersion`) are documented in the schema. The description adds no meaning beyond that, so baseline 3 applies.

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?

States a clear verb+resource ("Get image profile") and the qualifier "with a given id" hints at single-resource retrieval versus the sibling iaas_get_image_profiles. However, it never explains what an image profile actually is or explicitly contrasts itself with the list sibling, so the second and third lines merely restate the first.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., needing a valid image profile ID obtained from iaas_get_image_profiles), and no named alternative. The only implicit cue is the required `id`, which is already in the schema.

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