roles_get_role_assignments

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

No annotations are provided, so the description must carry the full burden. It mentions caching for 15 minutes and returns all users with pagination. However, it does not describe the response format, error conditions, or rate limits. For a read operation, this is moderately transparent but lacks detail about what user information is returned.

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 well-structured with separate sections for purpose, workflow tips, and common use cases, using bullet points and code examples. It is concise, with no redundant information, and every sentence adds value.

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?

Given the tool is a simple list endpoint with 3 parameters and no output schema, the description covers purpose, pagination, caching, and use cases. It lacks details on error handling or response format, but is sufficient for basic usage. The completeness is good for a low-complexity tool.

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% so parameters are already described. The description adds value with common use case examples showing how to use 'start' and 'limit' for pagination, clarifying default values and usage patterns 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?

The description clearly states it gets role assignments for a specific role, using the verb 'get' and specifying the resource 'role assignments'. It distinguishes from sibling tools like roles_add_role_assignment, roles_delete_role_assignment, and roles_get_role_settings by focusing on retrieval of users assigned to 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 provides workflow tips including pagination for many users and auditing, and gives common use case examples. It explains when to use pagination but does not explicitly state when not to use this tool or mention alternatives, though the sibling context provides differentiation.

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