Snowflake List Users

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds some value by disclosing what the listing returns (login status, default roles) and implicitly that it scans the whole account, but it says nothing about pagination, result size, or whether the pattern filter narrows scope.

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?

A single front-loaded sentence with no filler; the resource and the salient returned fields come first. Nothing here is redundant or padded.

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?

An output schema exists, so return values need not be spelled out, and the annotations carry the safety profile. But for a tool with an undocumented filter parameter and no usage framing, the definition is only minimally complete — it should say what the pattern filters and when to prefer this over describe_user.

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% for the single 'pattern' parameter, so the description is the only place semantics could be added — and it never mentions filtering or pattern syntax. The agent cannot tell whether 'pattern' is a name glob, a regex, or a case-sensitive prefix match.

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 specific verb and resource ('List users in the Snowflake account') and even previews the returned fields (login status, default roles). However, it does not distinguish itself from the nearby sibling snowflake_describe_user or explain how it relates to snowflake_list_roles/snowflake_list_grants_to_user, so an agent gets no routing help among those options.

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 when-to-use guidance, no stated prerequisites, and no mention of the obvious alternative (snowflake_describe_user for a single user). The description simply asserts what the tool does and leaves selection entirely to inference.

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