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

The annotations already declare readOnlyHint=true, so the description does not need to re-establish safety. It does add genuinely useful behavior beyond them: an empty list is returned when the user has no tweets, and pagination is cursor-driven. It omits permission/auth requirements, rate limits, and whether deleted or protected accounts alter results.

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?

Three short sentences, front-loaded with the core purpose and free of filler. Minor structural weakness: the empty-result and pagination notes are appended as separate fragments rather than consolidated, but nothing is redundant.

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?

The description never says how the 'specific user' is identified, and the schema exposes no visible parameters, so an agent has no documented way to bind the user or the cursor it is told to use. For a list/pagination tool with no output schema, this leaves the calling contract underspecified.

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?

With no documented parameters in the schema, the 4 baseline applies and the description does not need to explain parameter meaning. It actually gives one piece of parameter-adjacent guidance by tying `cursor` to pagination. It adds no clarification of how the target user is identified, which is the one detail an agent would want.

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 gives a specific verb and resource: 'Get tweets posted by a specific user.' That is clearer than the bare name and distinguishes it from reply/media siblings by scoping to posted tweets. It stops short of naming an alternative tool, so it lands at 4 rather than 5.

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 only usage instruction is 'Use `cursor` to paginate through results,' which is mechanical paging advice, not routing guidance. Nothing tells the agent when to prefer this over x_search, x_get_user_replies, or x_get_user_media, and there are no stated prerequisites.

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