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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful domain context (the role-on-scope model and the door-access equivalence) but says nothing about pagination behavior or result shape beyond what the schema already implies.

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?

Three compact clauses that front-load the core question ('Who holds which role where') before the filtering note and endpoint. Little waste, though the endpoint string 'GET /role_assignments' is decorative for an agent that cannot issue raw HTTP.

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 read-only list tool whose annotations carry the safety profile and with no output schema to explain, the description supplies the conceptual model (roles bound to organization/place/group, group membership equating to door access) an agent needs to route and interpret results correctly.

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 the schema already documents all 8 parameters, including enum values and pagination. The description's 'filter by user, group, place or role' only restates the filter surface at a high level and adds no syntax or format detail 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?

States a specific resource and, crucially, the exact semantics of what it returns: 'Who holds which role where' with roles on organization/place/group. The clarification that 'group members = door access' meaningfully distinguishes this from the sibling list_groups, even though no sibling is named explicitly.

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?

Usage is only implied by the phrase 'Filter by user, group, place or role' — the agent must infer that this is the tool for role/access-right queries rather than, say, kisi_list_groups or kisi_list_users. No when-to-use condition or explicit alternative is named.

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