browse_datastore

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

Annotations already cover read-only, idempotent, non-destructive safety, so the description adds value by explaining the return envelope and stating that all matches are returned so truncated is always false. It does not contradict any annotation, and adds meaningful behavioral context beyond structured metadata.

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?

Four short, purposeful sentences with no wasted words. The READ tag and primary use are front-loaded, followed by routing guidance, parameter sourcing, and return semantics. Every sentence earns its place.

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 straightforward read-only listing tool, the description covers purpose, when to use it, where required parameters come from, and the return envelope. Even without an output schema, it gives the agent enough information to invoke the tool and interpret the response correctly.

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 already provides 100% parameter descriptions, so the baseline is 3. The description adds value by linking 'glob' to the pattern parameter and sourcing ds_name from list_all_datastores, which helps an agent understand relationships between parameters and sibling tools.

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 verb and resource: 'Browse files in a datastore directory.' It also distinguishes itself from scan_datastore_images by explicitly routing deployable images to that sibling. An agent can tell exactly what this tool is for and what it is not for.

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?

Explicitly says when to use this tool ('arbitrary files or a glob') and names the preferred alternative for deployable images. It also tells the agent where ds_name comes from ('list_all_datastores'), removing ambiguity about a required parameter.

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