twitter_user_tweets_and_replies

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

Despite annotations indicating readOnlyHint and openWorldHint, the description adds significant behavioral context: it mentions pagination via cursor, item booleans (is_retweet, is_reply, is_quote) for filtering, and the overlap behavior with sibling endpoint. This goes beyond the annotations, which are minimal.

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 two sentences long, front-loaded with the primary purpose, and includes necessary filtering and pagination details without verbosity. Every sentence adds value, and the mention of sibling overlap is crucial.

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?

For a read-only list endpoint with no output schema, the description covers what the tool does, how to paginate, how to filter, and its relationship to a sibling tool. The complexity is moderate, and the schema already documents parameters well; the description fills the gap regarding response item booleans and overlap, making it complete.

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 parameters are well-documented in the schema. However, the description adds no additional param-specific meaning (e.g., examples or caveats). Since the schema covers everything, this is a solid baseline; the minor gap is not mentioning that 'cursor' is opaque but that is in 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?

The description clearly states it retrieves a user's full activity timeline, including original tweets and replies, which distinguishes it from the sibling tool twitter_user_tweets. It explicitly notes the overlap with twitter_user_tweets, making the distinction clear.

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 explains when to use this tool (understanding engagement with a community) and notes that twitter_user_tweets does not filter replies or retweets, so they may produce overlapping results. It does not explicitly list when not to use it, but the context implies alternatives may be redundant.

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