get_timeline

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose pagination behavior (cursor usage), rate limits, authentication requirements, data freshness, or what happens with seen_tweet_ids. For a read operation with 3 parameters, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration, making it easy to parse quickly.

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 tool's moderate complexity (3 parameters, read operation), no annotations, but with an output schema (which handles return values), the description is minimally adequate. It states the purpose but lacks parameter explanations and behavioral context that would make it complete for safe, effective use.

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 0%, so the description must compensate but provides no parameter information. It doesn't explain what 'count' controls (number of tweets), how 'cursor' enables pagination, or what 'seen_tweet_ids' filters. With 3 undocumented parameters, the description adds no semantic value beyond the bare 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 the verb 'Get' and the resource 'tweets from your home timeline', specifying it's for the 'For You' algorithmic feed. This distinguishes it from siblings like get_latest_timeline (chronological feed) and get_user_mentions (mentions). However, it doesn't explicitly contrast with all siblings like get_highlights_tweets or search_twitter.

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 retrieving the personalized home timeline feed, but doesn't explicitly state when to use this versus alternatives like get_latest_timeline (chronological) or get_user_mentions. No exclusions or prerequisites are mentioned, leaving some ambiguity about the optimal use case.

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