sec_rolePermissions

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

Annotations already declare readOnlyHint and idempotentHint as true, indicating safe read operation. The description adds valuable behavioral context: when persist is True, results are materialized as a volatile table and the table name is returned. This goes beyond annotations, clarifying a potential side effect (though volatile tables are temporary). No contradiction.

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 short and front-loaded with the purpose. The argument list is concise but redundant with the schema, slightly reducing efficiency. Still, every sentence serves a purpose. A more structured format could improve, but it is well above average.

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 explains the purpose and parameters, but does not specify the return format when persist is False (default). With no output schema, the agent is left to infer what 'permissions' look like. Other tools in the suite might provide this context, but for completeness, more detail on the default return would be helpful.

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?

Input schema has 100% description coverage for both parameters. The description's 'Arguments' section repeats those descriptions verbatim, adding no new meaning beyond what the schema already provides. Baseline score of 3 applies.

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 clearly states 'Get permissions for a role.' This directly specifies the verb (Get) and resource (permissions for a role), distinguishing it from sibling tools like sec_userDbPermissions (permissions for a user) and sec_userRoles (roles for a user).

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for analyzing role permissions, but does not mention when not to use it or provide comparisons with sibling tools. Usage is implied but not explicitly stated.

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