rbac_list_assignments

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

No annotations are provided. The description implies a read-only operation by stating 'List', but does not explicitly confirm idempotency or lack of side effects. It does disclose the 'active or all' filtering behavior, adding some transparency.

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 only essential information. It is front-loaded with the tool's purpose in a single sentence, containing no filler or redundant content.

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 no output schema and limited annotations, the description should provide more context about return format, permissions needed, or the meaning of 'active'. It fails to fully prepare an AI agent for correct usage beyond the basic purpose.

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 67% with agentId missing a description. The description only indirectly references agentId by saying 'for an agent'. The 'activeOnly' and 'now' parameters are described in the schema already, so the description adds little extra value. The missing agentId description is not compensated.

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 the verb 'List', the resource 'role assignments', and the scope 'for an agent' with the option 'active or all'. It distinguishes from sibling tools like rbac_assign_role, rbac_revoke_role, and rbac_check_permission which perform different actions.

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 does not provide any guidance on when to use this tool, such as prerequisites or alternatives. No mention of when not to use it or how it differs from similar tools like list_role_profiles.

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