iaas_enumerate_private_images_vmc

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

The 'POST /iaas/api/cloud-accounts-vmc/{id}/private-image-enumeration' line usefully signals this is a mutation-style trigger rather than a pure read, which aligns with readOnlyHint=false and non-idempotent. But it doesn't disclose that an enumeration is likely asynchronous or how the result is later retrieved, which is the behavior an agent most needs here.

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?

Single front-loaded sentence plus the endpoint path; nothing redundant. The raw path is slightly machine-ish but does convey the POST semantics in a few tokens.

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?

No output schema and no mention of what the call returns or that the enumeration result must be polled/fetched via a request tracker or region enumeration result endpoint. For a non-idempotent, open-world trigger this leaves a real operational 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 coverage is 100% and both parameters (id, apiVersion) are documented in the schema, so the description carries no burden here. It adds only the VMC-specific framing of the id; baseline 3 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?

States a specific verb and resource: enumerate private images for the enabled regions of a specified VMC account. The 'VMC' qualifier implicitly separates it from the aws/azure/gcp/vsphere/vcf siblings, though it never says so explicitly.

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 statement of when this should be called instead of e.g. iaas_enumerate_private_images or iaas_get_images, and no prerequisites (account must exist, must be enabled). The agent is left to infer everything from the name.

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