snowflake_list_grants_to_role

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List', implying read-only, but does not mention potential effects, return format, pagination, or any limitations. It adds very little beyond the tool name 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, succinct sentence that front-loads the core action and resource. There is no redundant wording, making it highly efficient and easy to parse.

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 simple one-parameter read tool with an output schema provided, the description is minimally adequate. However, it lacks nuance about what privileges are included (e.g., object-level vs account-level) and does not differentiate from the very similar grants_to_user tool beyond the role parameter. It covers the basics but leaves some context implicit.

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 0% description coverage, and the description does not mention the role_name parameter at all. Though the parameter is self-explanatory (a role name string), the description fails to add any additional meaning or clarify expectations, leaving the agent to rely on the name.

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 action ('List privileges granted') on a specific resource ('a specific role'), clearly distinguishing it from the sibling 'snowflake_list_grants_to_user' which targets users. It is unambiguous and directly names the resource being queried.

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 is given on when to use this tool over alternatives like snowflake_list_grants_to_user or snowflake_list_roles. There is no mention of prerequisites, context, or conditions where this tool is preferred, leaving the agent to infer usage 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.