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

Annotations already declare the safe read-only, open-world profile, and the description meaningfully adds to that: an explicit pagination contract (returns has_next_page + next_cursor, pass next_cursor as cursor) and a cost/rate model (13 credits per tweet, min 15 per call, waived on bulk). Auth needs and non-pagination output shape are not covered, keeping it short of a 5.

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?

Three tight lines, front-loaded with purpose, then pagination mechanics, then cost. Each sentence adds distinct, non-redundant information with zero filler.

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?

With no output schema, the description steps in to explain the pagination return fields and the credit cost, which is the information an agent most needs. It falls short of complete only because includeParentTweet and the exact includeReplies behavior remain unexplained for a 4-parameter tool.

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 carries the full burden, yet it only clarifies the cursor parameter (pass next_cursor as cursor). The required userId and especially the includeParentTweet toggle get no explanation, and includeReplies is only loosely implied by 'including replies'.

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?

States a specific verb (Return) and resource (a user's full timeline including replies), and pins the scope with a concrete analogy to the profile's posts-and-replies tab. It distinguishes itself from narrower siblings like user_last_tweets or user_mentions implicitly through the 'full timeline including replies' framing, though it never names an alternative.

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?

Usage is only implied through the 'full timeline including replies' scope, which suggests this is for complete history rather than targeted lookups, but no explicit when-to-use or when-not-to-use guidance is given and no sibling is named as the alternative.

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