image_list

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

The description discloses the read-only nature via [READ] and explains the limit parameter's behavior (capped read, returns 'returned', 'limit', 'truncated' for visibility). With no annotations, this provides complete transparency about side effects and constraints.

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 extremely concise: a single sentence summarizing purpose, followed by two parameter explanations. No redundant information; every sentence adds value.

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 list tool with two parameters and no output schema, the description covers purpose, parameters, and behavioral nuance (limit truncation). It could optionally mention that the list returns all images or any default filtering, but the current level is sufficient for agent invocation.

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 0% schema description coverage, the description fully compensates by explaining limit (max rows, default 500, truncation feedback) and target (optional Prism Central config name). This adds essential meaning beyond the raw schema types and defaults.

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 clearly states it lists content-library images and specifies the fields returned (extId, name, type, size, cluster placement). The [READ] tag distinguishes it from mutation tools, and the sibling list tools (snapshot_list, etc.) are for different resources, so the purpose is unambiguous.

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 implicitly indicates usage for reading image lists. While it doesn't explicitly state when not to use it (e.g., for deletion use image_delete), the [READ] tag and sibling names provide sufficient context. However, explicit guidance on alternatives would improve clarity.

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