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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the safety profile is free. The description adds the one thing annotations cannot: a concrete credit cost model (1 + 2 per profile + 1 per post), which materially affects call decisions for an agent with budget concerns. It does not mention rate limits or error surfaces beyond what the cursor schema already notes.

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, purpose front-loaded, no filler. Minor friction: '2 credits per profile returned' reads oddly for a single-account endpoint and briefly invites confusion about whether multiple profiles can come back.

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?

With no output schema, the description carries return-shape duty and partially discharges it by referencing meta.nextCursor and pagination. Cost and paging are covered; what is still missing is whether the returned posts include replies, reposts, or media-only items, which matters given the sibling tools that specialise in those.

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%, so baseline would be 3. The description goes one step further by naming the output field `meta.nextCursor` and tying it to the `cursor` input — useful because there is no output schema, so the agent otherwise would not know what to feed back. The `limit` and `user` semantics are left entirely to the schema.

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 ('Fetch recent posts from one public X account') plus ordering ('newest first'), which is enough to distinguish it from search_x or get_x_post. It does not, however, disambiguate against close siblings like get_x_user_replies or get_x_user_media, leaving the agent to infer whether replies/retweets are included.

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 pagination loop is spelled out explicitly ('When meta.nextCursor is set, call again with cursor set to it'), which is real when-to-use guidance. But there is no guidance on when to pick this over get_x_user_replies, get_x_user_media, or search_x — the most likely sibling confusions for this endpoint.

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