Lists the largest files in ESXi datastores or a selected datastore, shows owning VM, and flags potential orphans to help reclaim storage safely.
Archivos mas grandes de cada datastore (o de uno), con la VM a la que pertenecen y marca de posibles huerfanos.
| Name | Required | Description | Default |
|---|---|---|---|
| top | No | ||
| datastore | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose output content (VM ownership, orphan flagging), which is useful behavioral context, but says nothing about read-only status, required permissions, cost, or ordering — reasonable inference is a read tool, but it is never stated.
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?
A single dense sentence that front-loads the resource and enumerates the appended fields; no filler. Slightly parenthetical-heavy but efficient.
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?
For a 2-param, no-annotation, no-output-schema tool the description covers what is returned but omits the default behavior (all datastores, top 15), the meaning of 'top', and any read-only confirmation. Adequate but with clear gaps.
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 0%, so the description must compensate. '(o de uno)' explains that 'datastore' optionally narrows to a single datastore, and the 'largest files' framing hints at rank-based ordering, but the 'top' parameter is never explained as a count and the default of 15 is not mentioned.
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 clear resource (largest files) with scope (each datastore, or one) and the extra data returned (owning VM, orphan marking). An agent can tell what it produces, though it never distinguishes itself from the sibling 'datastores' tool.
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 or when-not-to-use guidance is given, and no alternative is named despite the closely related 'datastores' sibling. The optional datastore filter is implied by '(o de uno)' but not framed as a usage condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.