get_community_tweets

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

With no annotations, the description carries the burden. It discloses pagination behavior via cursor and next_cursor, and count limits. However, it does not explicitly state that it is read-only, nor does it mention authentication or rate limits. This is functional but not rich.

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 one-line summary plus a concise args list is efficient. Every sentence adds value, and the formatting is clean.

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 description is largely complete for a simple read tool: clear purpose, good parameter documentation, and pagination details. The output schema exists so return values are covered. The missing piece is usage differentiation from similar community tools, which keeps it from being a 5.

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?

Despite 0% schema description coverage, the description documents all four parameters with meanings, valid values for tweet_type, and default/max for count. This fully compensates for the schema's bare titles.

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 opens with a clear verb-object statement, 'Get tweets from a Twitter Community', and specifies pagination. This distinguishes it from sibling tools like 'get_community' or 'get_community_members' which focus on different resources.

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 gives parameter-level guidance (e.g., count limits, cursor usage) but does not explicitly state when to choose this over overlapping tools like 'search_community_tweet' or 'get_communities_timeline'. Usage is implied from the name but not contrasted with alternatives.

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