sec_userRoles

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

Description implies a read operation and mentions the persist option's behavior (materializes as volatile table). However, lacks details on error handling, required privileges, or behavior for non-existent users. Without annotations, this is adequate but not thorough.

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?

Description is a single sentence plus a structured argument list, front-loaded with purpose. No extraneous content, though the argument list duplicates schema information.

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 read tool, the description covers the main functionality and the persist option. However, it lacks output format details (except for persist), and there is no mention of error cases. Sibling tools create some ambiguity, but overall acceptable.

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%, and the description repeats the schema descriptions without adding new meaning. Baseline score of 3 applies as description does not enhance semantics beyond the schema.

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 roles assigned to a user,' specifying the verb and resource. It distinguishes from sibling tools like sec_rolePermissions and sec_userDbPermissions.

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 such as sec_rolePermissions or sec_userDbPermissions. No prerequisites or exclusions provided.

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