iaas_get_image_profiles

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, setting a low bar. The description adds nothing beyond restating the endpoint path—no pagination behavior, no filter semantics, no return shape, which is a meaningful gap for a list endpoint in an open-world API.

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?

It is short and front-loaded, but wastes space on three redundant restatements of the same thing ('Get image profile', 'Get all image profiles', the endpoint). Efficient in volume but low information density.

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 single-parameter read-only list tool with annotations covering safety and no output schema, the essentials are present. However, it omits pagination/return behavior and the differentiation from the singular sibling, leaving gaps an agent must guess.

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?

With 100% schema description coverage, the single apiVersion parameter is fully documented in the schema itself. The description adds no extra semantic detail beyond what the schema provides, so 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 uses a clear verb+resource ('Get all image profiles') and the plural form implicitly distinguishes it from the singular sibling iaas_get_image_profile, plus the raw endpoint disambiguates. The initial line 'Get image profile' is slightly confusing/redundant against the plural form, but the intent (list all image profiles) is decipherable.

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 guidance on when to use this list tool versus the singular iaas_get_image_profile, create/update/delete siblings, or iaas_get_images. No prerequisites, exclusions, or alternative-naming is provided; the agent must infer the use case from the endpoint.

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