sec_rolePermissions

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

The description explains that persist=True materializes a volatile table and returns its name, adding behavioral detail. However, it does not disclose whether the operation is read-only, any required permissions, or other side effects. With no annotations, this is a modest disclosure.

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?

Extremely concise with a clear two-line description and bullet-style parameter list. No unnecessary words, well-structured for quick reading.

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?

The description omits return format when persist=False, and does not explain the structure of the returned permissions (e.g., list of objects with columns). Given no output schema, this gap undermines completeness for a tool with only two parameters.

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 coverage is 100%, with both parameters described. The description adds value by clarifying the behavior of the 'persist' parameter (materializing and returning table name), which goes beyond the schema's 'If True, materializes...' note.

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?

Description clearly states 'Get permissions for a role' with a specific verb and resource. However, it does not differentiate from sibling tools like sec_userRoles or sec_userDbPermissions, which may overlap in purpose.

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. No prerequisites or context provided, leaving the agent to infer usage from the tool name and description alone.

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