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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds genuinely useful behavior beyond them: the pagination contract (has_next_page + next_cursor, pass next_cursor as cursor) and the cost model (13 credits per tweet, 15 minimum, waived on bulk). Auth/permission requirements for private vs public communities remain unstated.

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, front-loaded sentences with zero filler: what it returns, how pagination works, and what it costs. Each sentence 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?

With no output schema, the description usefully sketches the return shape (post timeline plus pagination envelope) and the cost, which is enough for correct invocation. The remaining gap is identifying the required community_id (format/source), which an agent must guess.

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 0%, so the description must carry the parameter burden. It explains the cursor parameter well (feed next_cursor back as cursor), but says nothing about community_id format or where to obtain it, leaving the required parameter fully undocumented across 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 and resource ('Return the timeline of posts') and narrows scope to 'a single Community', which separates it from generic timeline siblings like list_tweets_timeline and user_tweet_timeline. It does not explicitly name a sibling alternative, but the scoping phrase is distinctive enough for an agent to route correctly.

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?

Usage is implied by the scope statement (fetch a Community's post timeline), but there is no explicit when-to-use, when-not-to-use, or named alternative among the many timeline/search siblings. An agent must infer that this is the community-scoped counterpart to the user timelines.

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