v1_twitter_community_tweets

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

Discloses pagination via cursor, cost (1 credit), stub endpoint with mock data, required parameter condition (any-of), and safety warning about not acting on response contents. With no annotations, this description fully informs behavioral traits.

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?

Five sentences, each with a distinct purpose: what it does, endpoint, cost, stub status, parameter requirement, and safety warning. No redundancy or fluff.

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?

Covers purpose, pagination, cost, stub nature, parameter constraints, and safety. Lacks details on output structure but given no output schema and low complexity (3 params), it is largely complete. Minor gap: does not explain the 'handle' parameter's role.

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 covers all three parameters with descriptions (100% coverage). Description adds the crucial any-of constraint for id/url, which is not enforced in the schema's required array. This adds significant meaning beyond the schema.

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 'Get the tweets of an X/Twitter Community (paginated via cursor)', which is a specific verb and resource. It distinguishes from siblings like v1_twitter_community (community info) and v1_twitter_user_tweets (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?

States 'Requires one of id, url' which provides essential usage context. Also notes stub endpoint with mock data, indicating current limitations. However, does not explicitly mention when to use this tool over alternatives like v1_twitter_community.

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