snowflake_list_external_volumes

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

No annotations are provided, so the description must carry the behavioral disclosure burden. 'List' implies a read operation, but the description does not mention permissions, account-level scope, filtering behavior, or any side effects. It adds little beyond the operation name.

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 a single concise sentence with no superfluous words. It states the action and the resource immediately, making it easy to scan.

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?

The tool is relatively simple and has an output schema, so return values need not be described. However, the optional pattern parameter is completely unexplained, and there is no guidance on when to choose this tool over related list tools. This leaves meaningful gaps for an agent deciding whether and how to invoke it.

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%, and the single optional 'pattern' parameter is not mentioned in the description. Since the schema only provides the name 'pattern' with no description, the tool description should explain how pattern filters results, but it does not.

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 states a specific verb ('List') and resource ('external cloud storage volumes configured for Apache Iceberg tables'), so an agent can tell what the tool operates on. It does not explicitly contrast itself with sibling tools like snowflake_list_iceberg_tables or snowflake_list_stages, but the resource is distinct enough to make the purpose clear.

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?

There is no guidance on when to use this tool versus related list tools such as snowflake_list_iceberg_tables, snowflake_list_stages, or snowflake_list_integrations. The description only states what it does, leaving the agent to infer the appropriate context from the name alone.

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