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

Annotations only cover read-only/open-world safety, and the description goes well beyond them by disclosing the two operating modes (paged with TWITTER_BEARER_TOKEN vs a single embedded page without), that results may be a selection rather than the latest, the profile-page fallback, and a 1-credit cost. It does not describe the response shape or how cursor terminates, which keeps 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?

Purpose is front-loaded in the first short sentence, followed by payload contents, behavior modes and cost in descending importance. The fallback sentence is dense and slightly convoluted but each clause carries real information, so nothing is wasteful.

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, single-resource fetch with no output schema and 75% schema coverage, the description covers the important surprises: mode-dependent volume, non-chronological selection, fallback path and credit cost. The main remaining gap is any hint about the returned post fields, which an agent must infer.

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 coverage is 75%, so the schema already explains handle, count and cursor well. The description adds only indirect meaning for count (that its effective default and ceiling depend on which mode is active), which is useful framing but not new per-parameter detail; baseline 3 applies.

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 title and first sentence give a specific verb+resource: an account's public posts including media, likes, replies and retweets. That clearly separates it from siblings like twitter_tweet (single post) or twitter_profile (account info), though the description never names those siblings explicitly.

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 rather than stated: the tool is for retrieving an account's timeline, and the dual-mode paragraph hints at when results will be sparse. There is no explicit 'use twitter_tweet when you have a URL' or 'use twitter_communityTweets for community posts' routing guidance despite many close siblings.

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