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

Goes well beyond readOnlyHint=true: declares results are bounded to one page, that tokens are opaque and must be echoed rather than followed, that there is no automatic crawl, and lists the operational allowlist exclusions (payroll, national IDs, private contact/health data, free-text comments). This is the kind of safety/scope context an agent cannot infer from annotations.

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 tight sentences, each carrying distinct information: scope/verb, auth + pagination mechanics, and data-exclusion policy. Front-loaded with the core action, no filler.

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, no-output-schema list tool, the description covers auth, pagination contract, and data-exclusion policy. Minor gap: no indication of what fields a group record contains or how idIn narrows results, though the schema covers the latter.

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% and the description reinforces pageToken behavior (opaque, pass back for another page) without contradicting the schema. It says nothing about idIn filtering or pageSize bounds, which the schema itself documents, so the description adds only marginal value here.

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?

Names a specific verb+resource ('Read one bounded page of organization groups (including units/sections)') and clarifies that units/sections are the same resource. It is distinguishable from quinyx_get_group by the explicit 'page' framing, though no sibling is named.

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 clear conditions: required scope organization:groups:read, and 'pass pageToken for another page, no automatic crawl', which tells the agent how to iterate. It stops short of naming alternatives like quinyx_get_group for a single group or quinyx_list_employees for filtering by member.

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