browse_datastore

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

Annotations already cover read-only and idempotent hints, and the description adds valuable behavioral details: the return envelope structure and that 'All matches are returned, so truncated is always false'. This goes beyond the annotations without contradiction.

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 well-structured: a clear summary, usage guidance, return behavior, and parameter list. Every sentence contributes meaning, and the most important information is front-loaded.

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?

It covers purpose, usage context, parameter semantics, return format, and sibling relationships. With no output schema, the description's explanation of the response envelope and truncation behavior makes the tool self-contained for the agent.

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?

The input schema has no descriptions (0% coverage), but the description's Args section fully explains each parameter—ds_name, path, pattern, target—including defaults and examples. This perfectly compensates for the schema gap.

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 'Browse files in a datastore directory' and distinguishes itself from the sibling scan_datastore_images by explicitly saying to prefer that tool for deployable images. This makes the specific purpose and resource unambiguous.

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?

It gives explicit guidance: use for arbitrary files or a glob, prefer scan_datastore_images for deployable images, and mentions that ds_name comes from list_all_datastores. This provides clear context on when to use this tool and when not.

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