snowflake_list_roles

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

With no annotations, the description must carry the full transparency burden. It only says 'List roles' with no mention of permissions, read-only nature, or any limitations. It also fails to explain what 'available' means (e.g., roles visible to the current user vs all roles). The singular sentence provides minimal behavioral insight beyond the verb itself.

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, front-loaded with the verb and resource. It contains zero wasted words and is appropriately sized for a simple list operation.

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 one undocumented parameter and no annotations, the description is incomplete. It does not explain the behavior of the pattern parameter, nor does it specify any constraints or prerequisites. While an output schema exists (so return values are covered), the missing parameter semantics and lack of behavioral context make it insufficient for an agent to confidently 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%, meaning the 'pattern' parameter is completely undocumented in both the schema and the description. The description does not explain what the pattern does (likely filters role names by a pattern). This is a critical gap for a parameter that is optional but may significantly alter results.

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'), resource ('roles'), and scope ('in the Snowflake account'). This clearly distinguishes it from sibling tools like snowflake_list_users or snowflake_list_grants_to_role, leaving no ambiguity about what the tool does.

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?

The description is clear about the action but provides no explicit guidance on when to use this tool versus alternatives. Since there are many list_* siblings, some routing hint would help, but the simplicity of the operation (listing roles) makes the usage implicit. No exclusions or prerequisites are mentioned.

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