esxi_resource_schema

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false, so the safety profile is clear. The description adds that the tool returns a catalog of resource operations and accurate parameters, reinforcing its read-only discovery role, but it offers no further behavioral context such as caching, permissions, or output format (output schema exists).

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 a single concise sentence with a colon-separated list; it is front-loaded with the tool's role and avoids waste. The fragmented noun-phrase style slightly reduces clarity, but it remains 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?

The tool has annotations and an output schema, reducing the description's burden, and the domain list covers the key input. However, it omits usage guidance and leaves the 'action' and 'depth' parameters unexplained, so it is only partially 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 description coverage is 0%, so the description must compensate. It lists valid domain values (network, datastore, storage, etc.), which directly maps to the required 'domain' parameter, but it says nothing about the optional 'action' or 'depth' parameters. Partial compensation justifies a middle score.

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 names the resource domains it covers and calls itself a 'resource operation catalog and accurate parameters,' but it lacks a clear verb (e.g., 'retrieve schema') and does not distinguish itself from siblings like esxi_api_schema or esxi_resource_get. An agent can guess it provides schema details for the listed domains, but the purpose is not stated with the specificity of a verb+resource pair.

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, prerequisites, or alternatives are given. It does not say when to call this schema tool instead of esxi_api_schema, esxi_resource_get, or the domain-specific manage tools, leaving the agent to infer.

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