get_community_tweets

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

With no annotations, the description must fully convey behavioral traits. It mentions pagination but does not detail cursor-based pagination, authentication requirements, error scenarios (e.g., invalid community ID), or rate limits. The description is too sparse to adequately inform an agent about the tool's behavior.

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?

A single sentence with no extraneous words. It is front-loaded with the core purpose and is efficient.

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 lack of output schema and the presence of three parameters, the description is insufficiently complete. It omits details about pagination behavior, sorting defaults, and the response structure. For a tool retrieving a feed, users need more context on how to handle cursors and interpret results.

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 the parameters. The description adds no additional meaning beyond noting pagination, which the next_cursor parameter already implies. It does not elaborate on the order enum or community_id format.

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 tool retrieves a paginated feed of tweets from a specific X/Twitter community. The verb 'Get' and resource 'tweets published inside an X/Twitter Community' are precise, and it distinguishes from siblings like search_community_tweets (search vs. browse) and get_community_members (different resource).

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 implies usage for browsing a community's tweet feed but provides no explicit guidance on when to use this tool versus alternatives such as search_community_tweets for filtered queries. No when-not-to-use or prerequisite conditions are stated.

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