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

Annotations already establish readOnlyHint and openWorldHint, yet the description adds real operational context: result ordering (newest first), the pagination contract (has_next_page + next_cursor), and billing (13 credits per tweet, 15 minimum, waived on bulk). The only soft spot is that 'waived on bulk' leaves the threshold unstated, and auth/error behavior is not covered.

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 short lines, each earning its place: purpose and ordering first, then the pagination protocol, then cost. No repetition of the tool name or filler, and the most decision-relevant fact leads.

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 must carry return-value information, and it does disclose the pagination envelope (has_next_page, next_cursor). What the individual post objects contain is not described, which is a minor gap for a read-only listing 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 burden. It explains cursor semantics well ('pass next_cursor as cursor') but says nothing about listId beyond the resource name, leaving one of two parameters undocumented in both places.

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 first sentence states a concrete verb and resource with scope and ordering: 'Return the timeline of posts from a List, newest first.' The explicit 'from a List' plus 'newest first' separates it from user_tweet_timeline and community_tweets without opening a schema.

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 implied by the resource name, and the description does give the continuation procedure ('pass next_cursor as cursor for more'). However, it never states when to choose this over sibling timeline tools such as user_tweet_timeline or community_tweets, so alternative selection is left to inference.

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