get_datastore

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

Without annotations, the description fails to disclose behavioral traits such as read-only nature, authentication requirements, error handling for non-existent datastores, or rate limits. Merely stating 'Get datastore details' is insufficient for transparency.

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 extremely concise at one sentence, but this brevity sacrifices important details. It is front-loaded but lacks structure that could easily include parameter guidance or usage context without becoming verbose.

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 an output schema present, return values don't need description, but the tool still lacks context for input parameters, prerequisites, and precise purpose. The description is too minimal for a tool with 0% schema description coverage and no annotations.

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%, yet the description adds no explanation for the parameters 'datastore' (string identifier) and 'vcenter_name' (optional). Parameter names are somewhat self-explanatory but incomplete without clarifying expected format or source.

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 'Get datastore details' clearly indicates a retrieval operation for a datastore, distinguishing it from list_datastores which returns a list. However, it doesn't specify what 'details' entails, which could be more explicit.

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 on when to use this tool versus alternatives like list_datastores or other get_* tools. Lacks context about prerequisites (e.g., needing a datastore identifier from list_datastores).

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