iaas_enumerate_private_images_aws

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

Annotations already tell the agent this is a non-read-only, non-idempotent, open-world POST, and the description adds nothing beyond that. It does not disclose that this is an asynchronous enumeration job, whether it overwrites prior results, whether it costs quota/time, or how to poll progress — all critical for a trigger-style POST in a suite that has iaas_get_request_tracker and iaas_get_region_enumeration_result siblings.

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?

One front-loaded sentence states the core behavior efficiently. The appended raw 'POST /iaas/api/...' line merely restates the title/annotation and is dead weight, but the overall shape is tight.

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?

This is a state-changing, async enumeration trigger with no output schema, yet the description says nothing about what the call returns, whether it blocks, where results land, or how long it takes. For a non-read-only action tool with no output contract, that is a substantial gap.

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%, so both the account id and apiVersion are already documented in the schema. The phrase 'specified AWS account' mildly reinforces that id must be an AWS cloud account, but adds no format, default, or version-negotiation detail beyond the schema.

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 specific verb and resource ('Enumerate all private images') scoped to an AWS cloud account's enabled regions, so the operation is unambiguous. It implicitly differentiates from the azure/gcp/vsphere siblings via the account scope, but never names those siblings or the generic iaas_enumerate_private_images variant.

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 when-to-use versus when-not guidance, no mention of prerequisites (regions must already be enabled) and no pointer to how the enumeration result is retrieved. The agent must infer everything from the tool name and the bare REST path.

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