scan_datastore_images

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds that it's a live scan, explains the return envelope (items/returned/total/truncated), and guarantees truncated is always false. It does not go into auth or performance, but adds meaningful context beyond the annotations.

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 well-structured: a concise summary, usage guidance, return format, and parameter list. Every sentence adds value; no filler.

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?

With no output schema, the description adequately describes the response envelope and the guarantee about truncation. It could be more explicit about what fields each image row contains, but given the tool's simplicity, it is largely complete.

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 has 0% description coverage, so the description's Args section is essential. It explains ds_name as the datastore name, path as subdirectory (empty for root), and target as optional vCenter/ESXi target, providing meaning that the schema lacks.

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 opens with '[READ] Scan a datastore for deployable images (OVA, ISO, OVF, VMDK)', clearly stating the action and resource. It differentiates from list_cached_images by framing this as a live scan, and references sibling list_all_datastores for ds_name.

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?

Explicitly says 'Use this for a live scan of one datastore; prefer list_cached_images for a cached answer' and notes that ds_name comes from list_all_datastores, giving clear when-to-use and alternative guidance.

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