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

With no annotations, the description carries the full burden, and it only discloses one behavioral trait: home requires authentication. It says nothing about pagination via 'before', rate limits, or what 'ranked' vs 'status' actually changes in the result set.

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?

It is a single front-loaded line with no filler, which is structurally good, but the pipe-separated fragment is cryptic enough that brevity comes at the cost of comprehension rather than earning its place as clear conciseness.

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 4-parameter tool with 0% schema coverage, no annotations, no output schema, and a likely-overlapping sibling (hiveposts_feed), the description is far too thin to let an agent call it correctly or choose between it and its alternatives.

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 compensate, but it only names three of the four mode values (omitting 'new') and says nothing about limit, before, or the lite/full fields toggle. This leaves most parameters undocumented anywhere.

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?

It states the resource (a timeline) and gestures at modes with 'X-style timeline', but never says what a timeline actually returns or how it differs from the sibling hiveposts_feed, which plausibly overlaps. The mode list is a parameter hint rather than a purpose statement.

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 guidance is the parenthetical '(home needs auth)', which is a prerequisite rather than a when-to-use rule. It gives no indication of when to prefer this over hiveposts_feed or the other feed-like siblings, and no exclusions.

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