list_images

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

Without annotations, the description only says 'list' which implies read-only. It does not disclose pagination behavior, default number of results, or any side effects. The ordering note is helpful but insufficient.

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?

While very brief (one sentence), it sacrifices necessary detail. Conciseness should retain completeness; here it omits crucial information about parameters and behavior.

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?

Given 6 parameters, no output schema, and no annotations, the description fails to cover essential aspects like filtering, pagination, what an 'image' is, or how results are sorted beyond 'newest first'. This is inadequate for agent decision-making.

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 0%, yet the description provides no explanation for any of the 6 parameters. Parameters like compartment_id, operating_system, shape, limit, page are left completely undefined.

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 the verb (list) and resource (platform images), and adds ordering ('newest first'). It distinguishes from sibling tools that list other resources. However, it lacks specificity about what constitutes 'platform images'.

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 on when to use this tool versus alternatives like list_instances or list_buckets. No context on prerequisites or limitations.

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