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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral context beyond them: pagination semantics (has_next_page + next_cursor, ~20 per page) and an explicit cost model (13 credits per tweet, 15 minimum, waived on bulk). It does not describe rate limits or auth requirements, but for a read tool this is above-average 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?

Four short, front-loaded lines that each carry information; the paging and credit facts are separated cleanly. Minor redundancy: 'newest first' appears twice, wasting part of a very short text.

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, yet the description compensates by naming the returned paging fields (has_next_page, next_cursor), which is exactly what an agent needs for iteration, plus a cost model. The only material omission is any explanation of includeReplies and of how this feed differs from sibling timeline tools.

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 0%, so the description must carry parameter meaning, and it does explain userName vs userId (either/or), cursor (pass next_cursor), and the ~20-per-page page size. However the includeReplies parameter is never mentioned or explained, leaving one of four parameters undocumented in both schema and description.

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+resource+scope ('a user's most recent posts and reposts, newest first'), which is clear enough to distinguish from sibling feeds like user_mentions. However it never contrasts itself with the very similar siblings user_tweet_timeline or tweets, so the agent cannot be fully certain which to pick from the name alone.

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?

Gives parameter-level usage guidance ('Pass userName (handle) or userId') and explains paging continuation via cursor, which is genuinely useful. But it offers no when-to-use/when-not guidance relative to overlapping siblings such as user_tweet_timeline, so usage context is only implied.

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