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

Annotations only declare readOnlyHint, and the description adds substantive context beyond that: the required organization:roles:read scope, the fact that pagination is caller-driven with no automatic crawl, and an operational allowlist that excludes payroll, national IDs, private contact/health data and free-text comments. That last point materially shapes what an agent can expect in the payload.

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?

Four short sentences, front-loaded with the operation and scope, then paging, then data-exclusion policy. No repetition and every sentence carries distinct 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 two-param read-only list tool with no output schema, the description covers the permission prerequisite, the return shape in outline (data plus opaque pagination tokens), how to continue paging, and the data-exclusion policy. Nothing an agent needs to call it correctly is missing.

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 pageSize and pageToken are already documented, including that the token is opaque and never a URL. The description reinforces the pageToken usage ('pass pageToken for another page, no automatic crawl') but adds no format or boundary detail beyond the schema, so baseline 3 applies.

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 verb+resource ('Read one bounded page of organization roles') and the paging scope makes it distinguishable from the single-record quinyx_get_role. It never names a sibling explicitly, so the list-vs-get routing is left implicit.

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?

Gives the required permission scope and explicit paging instructions ('pass pageToken for another page, no automatic crawl'), which tells the agent how to iterate. It stops short of stating when to prefer this over quinyx_get_role or quinyx_list_role_assignments.

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