scan_datastore_images

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that results are cached locally and that it scans all accessible datastores, which provides useful context beyond what annotations offer.

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 very concise: a two-sentence purpose statement followed by a one-sentence parameter definition. Every sentence adds value, and the key action is front-loaded.

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 the tool is simple (one optional parameter, no output schema), the description covers its purpose, caching behavior, and parameter usage. It could mention that scanning multiple times refreshes the cache, but the idempotent hint covers that implicitly.

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?

The only parameter (target) has no schema description, but the description clearly explains it as 'Optional vCenter/ESXi target name from config,' adding essential meaning beyond the schema's type definition.

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 scans datastores for deployable images (OVA/ISO/OVF/VMDK), using a specific verb and resource. It distinguishes itself from sibling tools like list_vcenter_alarms or vm_power_on by specifying its unique function.

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 says 'Run this to refresh the cache' and mentions that results are cached for fast lookup via list_cached_images, providing clear context. However, it does not explicitly state when not to use this tool or list alternatives beyond the caching sibling.

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