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

With readOnlyHint/destructiveHint already covering safety, the description adds real behavioral value: the result cap and popularity-based ordering, the exact returned fields, a trim option, and that completed lookups cost at least 10 credits and repeated requests may re-purchase data. The pricing block is internally muddled ('at least 10 Nexscope credits' vs. '1 credit per request' vs. 'examples are not guaranteed prices'), which weakens otherwise strong cost disclosure.

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 first two sentences are well front-loaded and high value. The trailing pricing paragraph is verbatim vendor boilerplate with duplicated phrasing ('Twitter User Tweets API View Pricing Get up to 100 popular tweets...') that bloats the definition and reads awkwardly.

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?

There is no output schema, so enumerating returned fields (rest_id, counts, created_at, media, url) is genuinely necessary and present. Combined with the result-cap caveat and cost note, an agent has enough to decide and call correctly; only error/invalid-handle behavior is unaddressed.

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 100%, with both handle and trim already documented in the schema. The description only restates trim as 'a lighter response' and adds no format guidance for the handle (e.g., with or without @), so the schema carries the load.

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?

Opens with a specific verb+resource: 'Fetches tweets from a Twitter user's profile by handle,' which is clearly distinct from siblings like social_twitter_tweet (single tweet) or social_twitter_search_posts (query-based search). It does not name those siblings explicitly, but the handle-scoped framing is unambiguous.

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 gives crucial usage context: results are ~100 popular tweets, 'not chronological or latest,' which prevents an agent from misusing this as a timeline feed. It stops short of naming the alternative tool an agent should call when it needs recent/chronological posts.

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