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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower, and the description still adds real behavioral detail the annotations cannot express: fixed page size of 20 and newest-first ordering. It omits rate-limit or truncation behavior, but what it does add is genuinely useful for planning pagination.

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 short sentences, front-loaded with the purpose and followed by the pagination mechanic. Nothing is padded and nothing essential is buried.

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 only two parameters, full schema coverage, and complete annotations, the description supplies the remaining operational facts an agent needs: ordering, page size, and how to continue paging. Only a note on result limits or how to treat an exhausted cursor would round it out.

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%, with both community_id and cursor (including the 'omit or "" for the first page' rule and the next_cursor reference) documented in the schema itself. The description only contributes the page-size constant and ordering, which is marginal added meaning beyond the schema — the baseline 3 fits.

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?

Specific verb ('Get') plus resource ('tweets from an X Community') with a scope hint ('newest first'). It is clear what the tool returns, though it never names or contrasts with the sibling search_community_tweets, which is the most likely confusion point for an agent.

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 purpose statement and by 'use cursor to paginate', which gives procedural guidance for paging. However, there is no explicit when-to-use vs. when-not, and no hint about when to prefer search_community_tweets over this listing call.

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