List the roles assigned to a user

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, indicating a safe, non-destructive operation. The description adds the permission requirement 'Perm: manage_users', which is useful but not extensive. No contradictions exist.

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 extremely concise with two sentences that directly state the purpose and permission requirement. Every word adds value, and no extraneous information is present.

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 tool has an output schema (as indicated by context signals) and the schema covers all parameters, so the description doesn't need to explain return values. It adequately covers the core purpose, though it could optionally mention pagination-related parameters (from, limit, cursor) for completeness.

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 100%, so all parameters are documented in the schema. The description adds no additional parameter-specific meaning beyond the schema, earning a baseline score of 3.

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 explicitly states that the tool lists roles assigned to a user, specifying it retrieves roles by user ID. This clearly defines the verb (list) and resource (roles), and distinguishes it from sibling tools like action1_list_roles (which lists all roles) and action1_list_role_users (which lists users for a role).

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 usage when needing roles for a specific user but provides no explicit guidance on when to use this tool versus alternatives, such as action1_list_roles or action1_list_role_users. It mentions a required permission (manage_users) but lacks when-not usage or alternative recommendations.

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