browse_datastore

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds a '[READ]' tag and parameter descriptions but does not disclose behavior beyond annotations (e.g., error handling or edge cases).

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: a one-line summary followed by a bulleted Args list. Every sentence is necessary, no fluff.

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 annotations cover safety and the output schema exists, the description sufficiently specifies all parameters and usage. It includes example patterns and explains default behavior for path and pattern.

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 fully carries the burden. It explains each parameter clearly: ds_name (datastore name), path (subdirectory, root if empty), pattern (glob filter, e.g., '*.ova'), and target (optional vCenter/ESXi target). This adds essential semantics.

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 tool's purpose: 'Browse files in a datastore directory.' This verb-resource combination distinguishes it from sibling tools like list_all_datastores (lists datastores themselves) and scan_datastore_images (scans for images).

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 implies usage for browsing datastore files but does not explicitly state when to use this tool over alternatives (e.g., scan_datastore_images). No when-not-to or specific scenarios are provided.

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