get_community_tweets

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

The description explains pagination behavior and cursor usage beyond the schema, but with no annotations, it could disclose more about rate limits or authentication. However, it sufficiently covers the read-only nature and result structure.

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 concise with a clear one-line purpose and well-structured parameter list. Every sentence adds value without redundancy.

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?

Given the presence of an output schema and 4 parameters, the description covers the parameters well but does not mention potential authentication requirements or community membership prerequisites. Still, it is fairly complete for a read tool.

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?

The description adds crucial meaning beyond the schema: it specifies that tweet_type accepts 'Top', 'Latest', or 'Media', defines count defaults and max, and explains cursor as a pagination token from previous responses. This compensates for the 0% schema coverage.

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 it retrieves tweets from a Twitter Community with pagination. The verb 'Get' and resource 'tweets from a Twitter Community' are specific and distinguish it from siblings like get_timeline or get_user_tweets.

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 does not provide explicit guidance on when to use this tool versus alternatives like search_community_tweet or get_community. It implies usage for fetching community tweets but lacks when-not-to-use or alternative recommendations.

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