snowflake_list_row_access_policies

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

No annotations are provided, so the description carries the full behavioral burden. 'List' reasonably implies a non-mutating read operation, but the description does not disclose authorization requirements, pagination behavior, or potential limits. It is adequate for a simple list operation but not rich in behavioral detail.

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. Every word contributes to identifying the operation and its scope, making it easy for an agent to parse quickly.

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 low-complexity read-only listing tool with an output schema, the core resource and scope are present, and return-value details are covered by the output schema. However, the missing semantics of 'pattern' and the exact default behavior when no database or schema is supplied leave the description minimally viable rather than complete.

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%, so the description must compensate for the undocumented parameters. It does clarify that database and schema_name define scope and implies account-wide listing when they are omitted, but it says nothing about the pattern parameter's format or behavior. This is only partial compensation for a schema with no parameter descriptions.

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 uses a specific verb ('List') and a specific resource ('row access policies'), and clarifies scope as account, database, or schema. This clearly distinguishes it from the sibling snowflake_describe_row_access_policy, which is a single-policy detail 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 provides clear scoping context ('account, database, or schema') that signals the intended use for enumeration. However, it never explicitly mentions alternatives or exclusions, such as using snowflake_describe_row_access_policy when only one policy's details are needed. The distinction is implied by the verb rather than stated.

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