getUserTimeline

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action ('Get') without mentioning pagination behavior (implied by 'pagination_token' parameter but not explained), rate limits, authentication requirements, error conditions, or what format/scope the timeline includes. For a retrieval tool with 11 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 extremely concise with a single sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. It's appropriately sized for a retrieval operation and front-loads the essential information.

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 complexity (11 parameters, no output schema, no annotations), the description is insufficiently complete. It doesn't explain what a 'timeline' entails (chronological posts? includes retweets?), how results are structured, pagination behavior, or error handling. For a data retrieval tool with many filtering options, more context is needed to use it effectively.

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 no parameter-specific information beyond what's already in the schema (which has 100% coverage). It doesn't explain relationships between parameters (e.g., how 'start_time'/'end_time' interact with 'since_id'/'until_id'), provide examples for complex fields like 'expansions', or clarify the timeline's chronological order. With complete schema coverage, the baseline is 3.

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's purpose: 'Get a user's timeline of posts' specifies the verb ('Get') and resource ('user's timeline of posts'). It distinguishes from some siblings like 'getSinglePost' or 'getUserBookmarks' by focusing on a chronological feed, but doesn't explicitly differentiate from all similar retrieval tools like 'getUserMentions' or 'searchRecent'.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate compared to siblings like 'getUserMentions' (for mentions timeline), 'searchRecent' (for keyword-based timeline), or 'getLikedTweets' (for liked posts). No exclusions or prerequisites are stated.

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