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

readOnlyHint=true already covers the safety profile, so the description earns credit for adding real context beyond annotations: the required permission (organization:groups:read) and the fact that payroll/private fields are omitted from results. It stops short of describing the not-found behavior or response shape.

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 short sentences, with the addressing modes and the permission requirement front-loaded ahead of the field-omission caveat. No wasted clauses, though 'documented external reference' is slightly vague where 'xrefId' would be precise.

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 single-parameter read tool with readOnlyHint annotation and no output schema, the description covers the essential calling information: how to address the group, the needed scope, and the fact that some fields are withheld. The absence of return-value detail is the only meaningful gap.

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% and the schema already documents 'Internal numeric ID or xrefId:external-id', which the description essentially restates. It adds only the qualifier that xref IDs are 'documented', giving no extra format or constraint 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 verb and resource ('Read operational group metadata') plus the two addressing modes, which is enough to distinguish it from a generic group operation. It does not explicitly name quinyx_list_groups as the listing counterpart, so sibling differentiation 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?

'By internal numeric ID or documented external reference' implies you should use this when you already hold an identifier, and the required scope hints at prerequisites. However, it never says when to prefer this over quinyx_list_groups or what to do when you lack an ID.

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