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

readOnlyHint=true already covers the safety profile, and the description adds useful context beyond it: the exact fields returned, pagination behavior, and the underlying endpoint. It does not mention rate limits or ordering, but for a read-only list this is a solid add over the 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?

A single compact sentence that front-loads the resource and returned fields, with the endpoint as a trailing technical note. 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?

With no output schema, the description compensates by listing the returned fields and noting pagination; input parameters are fully covered by the schema. Only minor gaps remain (ordering, empty-result behavior).

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 both parameters (page, page_size) are fully documented in the schema, so baseline 3 applies. The description only echoes 'paginated' and adds no format or default 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 (List) and resource (portal's groups), enumerates the fields returned (id, name, description, branch, price, key redemptions), and names the endpoint GET /api/v2/groups. An agent can distinguish it from talentlms_get_group (single) and talentlms_list_group_users (membership-scoped) without opening a schema.

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 implied by the verb and scope — a paginated collection read — but there is no explicit when-to-use/when-not statement and no naming of alternatives such as talentlms_get_group or talentlms_list_group_users. The agent must infer selection from the verb alone.

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