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

Annotations already declare this a safe, idempotent, open-world read (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds genuinely new behavioral facts beyond the annotations: newest-first ordering, inclusion of retweets and the pinned tweet, and pagination. It stops short of describing auth requirements or pagination semantics beyond 'Paginated'.

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?

A single front-loaded sentence that packs scope, ordering, content inclusions, and pagination with no filler. Every clause earns its place.

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 6-parameter read tool with an exceptionally rich schema and no output schema, the description covers content scope, ordering, and pagination adequately. It omits any note that an identifier (userId or username) is effectively required, leaving that to the schema.

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 100%, so the schema already documents count, cursor, format, userId, username, and max_chars with defaults and constraints. The description only alludes to pagination and adds no parameter-level detail, so the 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?

States a specific verb and resource ('Get a user's recent tweets') and immediately scopes it ('their profile timeline, without replies'), which cleanly separates it from the sibling get_user_tweets_and_replies. An agent can pick this tool without opening either 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?

The 'without replies' clause implies when this tool is preferred over get_user_tweets_and_replies, but that sibling is never named and there is no explicit when-to-use or exclusion guidance. Usage is inferable rather than stated.

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