get_community_moderators

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

No annotations are provided, so the description must carry the behavioral transparency burden. It discloses that results are paginated and explains the cursor/count mechanics, which is useful. However, it does not mention authorization requirements, error behavior, or rate limits, which could be important for a production API call. The transparency is moderately sufficient for a simple read operation.

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?

The description is succinct, starting with the core purpose in one line, then an args list with no filler. Every sentence/line adds value, adhering to front-loaded and concise formatting.

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?

The tool is simple and the description explains the purpose, all parameters, and pagination. It doesn't cover error conditions or response format, but an output schema exists to handle return values. Overall it offers a complete picture for basic usage, though not exhaustive.

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%, but the description compensates by listing each parameter and providing semantics: community_id is the target community, count has a default of 20 and max of 100, and cursor references the previous response's next_cursor. This adds significant meaning beyond the raw schema, especially for count and cursor.

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 clearly states the operation: 'Get moderators of a Twitter Community (paginated).' This distinguishes it from sibling tools like get_community_members or get_community_tweets, making its specific purpose immediately obvious. The pagination note adds useful scope.

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?

The description provides clear context for when to use this tool—to retrieve community moderators—and explains pagination usage with cursor and count, but it does not explicitly mention alternatives or exclude other tools. There is no comparison to sibling tools such as get_community_members, so guidance on selection is only implied by the name.

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