storage_rescan

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

Annotations indicate readOnlyHint=false, confirming mutation, but the description adds no behavioral context such as potential disruptions, safety considerations, or what changes occur. The destructiveHint=false conflicts slightly with write nature but is not explained.

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 concise with two sentences plus an Args list, avoiding extraneous information. Slight improvement could be made in readability by integrating the Args into the main description.

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?

Despite an output schema being present, the description omits crucial context about when rescans are needed, potential side effects, error conditions, or how it fits with siblings like scan_datastore_images.

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?

With 0% schema description coverage, the description merely lists the parameters already in the schema (host_name, target) without adding meaning, format, or constraints beyond what the schema provides.

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 'Rescan' and the specific resources 'all HBAs and VMFS volumes' on an ESXi host, distinguishing it from sibling tools that are read-only or target different storage aspects.

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 is provided on when to use this tool versus alternatives. The '[WRITE]' prefix hints at a write operation, but no contextual cues about prerequisites, triggers, or exclusions are given.

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