arcane_browse_volume

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

With no annotations, the description must disclose behavioral details itself. It merely states 'Browse files in a volume' without explaining what browsing entails, such as whether it returns a listing, whether it is recursive, or any side effects. This is a significant transparency gap for a tool that needs to be invoked correctly.

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 very concise, just six words, which is efficient. However, it is under-specified; it could be slightly expanded to convey more useful information without becoming verbose. The single-sentence structure is appropriate but does not maximize its limited length.

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 tool with three parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the browse operation returns, whether path defaults to root, or any other contextual details needed for correct invocation. This is far below the minimum viable completeness for a tool of this complexity.

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 provides descriptions for all three parameters (environmentId, volumeName, path) with 100% coverage. Since the schema already documents the parameters, the baseline score is 3. The description adds no additional parameter semantics, but it is not required to compensate.

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 uses the specific verb 'browse' and the resource 'files in a volume', clearly indicating the tool's purpose. It is understandable on its own, though it does not explicitly distinguish itself from the sibling 'arcane_get_volume_file', which could also involve file access.

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 usage guidance is provided. The description does not specify when to choose this tool over alternatives, mention prerequisites, or offer any context about use cases or limitations.

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