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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to cover safety. It adds useful behavior beyond annotations by stating that the result is a list and that a cursor is used for pagination, which is actionable for agents. No contradictions with annotations.

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 sentence with a brief parenthetical note on pagination. It is front-loaded with the core purpose and includes only essential additional information, with no 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?

For a read-only list tool with a fully described schema, the description covers the main purpose and pagination behavior. It does not need to repeat parameter details or output format since those are either in the schema or not applicable (no output schema). Missing details like rate limits or authentication are not critical given the annotations.

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 descriptions cover all 5 parameters (handle, limit, cursor, includePinned, includeReplies) at 100% coverage. The description merely reinforces 'by handle' without adding any new semantic detail, so it falls at the baseline for high schema coverage.

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 (list), resource (tweets from an X profile), and the primary parameter (handle). It distinguishes this from sibling tools like twitter_tweet_get (single tweet) and twitter_tweet_replies_list (replies), leaving no ambiguity about its function.

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 a specific user's tweets based on the handle, but it does not explicitly contrast with alternatives such as twitter_search_list or twitter_community_tweets_list. No when-to-use or when-not-to-use guidance is given beyond the implicit context.

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