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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful pagination behavior (fixed page size of 20, cursor-driven paging), which goes beyond the annotations, but it says nothing about permissions, ordering, or result 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?

Two compact, front-loaded sentences with no filler: the purpose comes first and the pagination constraint follows. Nothing is wasted, though the second sentence could have carried slightly more useful detail.

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 simple two-parameter read tool with full schema coverage, rich annotations, and no output schema, the definition supplies what an agent needs to call it correctly, including page size and cursor mechanics. Only the nature of the returned moderator records is left unstated.

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 100%, so both community_id and cursor are already documented, including the 'omit or empty string for first page' detail. The description merely restates the cursor pagination, adding no new meaning 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?

The description names a specific verb and resource ('Get moderators of an X Community'), which clearly distinguishes it from sibling reads like get_community_members or get_community_info. It stops short of explicitly contrasting with alternatives, but the resource itself is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance; the only operational note is pagination. An agent must infer that this tool is for listing moderators rather than members, and no prerequisites or alternative paths are mentioned.

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