get_community_members

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

No annotations provided, so description carries full burden. It only describes the tool as 'paginated' without disclosing key behaviors such as authentication requirements, rate limits, or error handling when community_link is invalid.

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?

Single sentence of 11 words, efficient and front-loaded with essential information. No superfluous content.

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?

No output schema and no description of the response structure. For a paginated tool, the description should mention that the response includes a next_cursor for further pages, but it does not. The parameter next_cursor alludes to this, but the description is incomplete without explaining the return format.

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 the schema already documents both parameters adequately. The description adds little beyond the schema, providing context of pagination but no additional parameter semantics.

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?

Description clearly states the tool retrieves a paginated list of member profiles from a community. The verb 'Get' and resource 'member profiles' are specific, and the context 'of an X/Twitter Community' distinguishes it from siblings like get_community_tweets and check_community_member.

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?

Description lacks any guidance on when to use this tool versus alternatives. Among siblings, check_community_member checks a single member, but no mention of this or other context for use.

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