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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results come back paginated ("a page at a time"), which is genuinely useful beyond the annotations, but says nothing about ordering, page size, what a "role" contains, or whether the caller must be an org member.

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 front-loaded sentence with zero filler. Its brevity is efficient, though in this case brevity coincides with under-specification rather than tightness.

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 paginated membership-listing tool with three undocumented parameters and no output schema, the description should at minimum describe the page object shape and the role field. Annotations cover the read-only safety profile but leave the agent unable to call this confidently.

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 0%, so the description bears the full burden for org, limit, and cursor. It only obliquely signals cursor-style paging; it never explains that org is the org identifier, what limit defaults to or its maximum, or how cursor chaining works.

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?

"An org's members and roles" identifies the resource and implies a listing, and "a page at a time" implies pagination. But there is no explicit verb (list/read) and no differentiation from sibling tools like org_members_add, org_member_remove, group_members, or team_members, so an agent must infer that this is the read-side counterpart.

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?

No when-to-use guidance, no exclusions, and no pointer to alternatives. The description never says to use org_members_add for mutations or group_members/team_members for other membership scopes, even though those siblings exist and are easy to confuse with this one.

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