iso_list_isos

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the sidebar action and adds nothing about side effects, read-only status, data scope, or pagination. The verb 'list' implies a read operation, but that is not explicitly stated.

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 very short, which is good, but the 'Returns:' line is redundant with the first sentence, repeating 'List of available ISO images'. The content is front-loaded, but the duplication makes it less efficient than a single crisp sentence.

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?

While simple, the description omits any reference to the sibling list variants (public, custom) that an agent might need to choose between. The output schema exists, so return value details are covered, but the decision context is missing.

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?

The tool has zero parameters secret and the schema documents 100% of them (none). The description does not need to explain parameter semantics, so the baseline of 4 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?

The description uses a specific verb ('List') and resource ('available ISO images'), making the tool's basic function clear. However, it does not distinguish itself from the sibling tools iso_list_public_isos and iso_list_custom_isos, relying on the phrase 'all available' to imply breadth.

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 given on when to use this tool versus the more specific sibling tools like iso_list_public_isos or iso_list_custom_isos. An agent would not know whether to choose this tool or a filtered alternative based on the description alone.

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