snowflake_list_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the output includes login status and default roles, but does not clarify whether the optional pattern filters results, what permissions are required, or any potential side effects. Since this is a read operation, the lack of explicit safety indication is acceptable, but the pattern behavior is undisclosed.

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, concise sentence that conveys the core purpose with no filler. It is appropriately sized for a simple list operation and front-loads the action and resource.

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?

While an output schema exists (so return format is covered), the description leaves the sole parameter 'pattern' completely unexplained. For a tool with one optional parameter, this is a significant gap. The agent cannot determine how to filter or whether the parameter is a LIKE pattern, exact name, etc.

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 schema has one parameter 'pattern' with no description (0% coverage), and the description does not mention it at all. An agent has no idea what format or semantics to use for the filter. The description fails to compensate for the schema's lack of parameter documentation.

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 ('users in the Snowflake account') and adds output details ('with login status and default roles'). It clearly distinguishes this from sibling tools like snowflake_describe_user (single user) and snowflake_list_roles (roles), making the intent 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?

No guidance on when to use this tool versus alternatives. It does not mention that this lists all users in the account, nor does it contrast with snowflake_describe_user for individual lookups. An agent would have to infer usage from context.

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