snowflake_list_grants_to_user

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

No annotations are provided, so the description carries the full burden. The verb 'list' implies a read-only operation, but the description does not explicitly state that it is non-destructive, does not require special permissions, or mention any other behavioral traits like pagination or result limits. For a simple list operation, this is minimally adequate but not rich.

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 sentence with no filler. It is front-loaded with the action verb and directly states what is returned, making it highly concise and efficient.

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?

Given the simple single-parameter scope and that an output schema exists (which presumably details return values), the description is complete for an agent to call the tool correctly. It could mention that it returns only roles (not all grants) or any prerequisites, but the current text is adequate for the operation's simplicity.

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 only defines user_name as a string with no description (0% coverage). The description's phrase 'to a specific user' clarifies that the parameter is the user whose roles are listed, adding meaning beyond the schema. For a single obvious string parameter, this is sufficient context.

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 'List roles granted to a specific user' uses a specific verb (list) and resource (roles granted to a user), clearly distinguishing it from siblings like snowflake_list_grants_to_role (roles granted to a role) and snowflake_list_roles (all roles). The meaning is unambiguous and directly tied to the operation.

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 implies when to use this tool (when you need the roles for a specific user), but it does not explicitly mention alternatives or exclusions. There is no guidance on when not to use it or how it differs from similar tools, so it relies on inference.

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