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

Goes beyond the readOnly/openWorld annotations by disclosing the auth requirement ("Requires a prepaid API key") and the nature of results (compact, each item carries a url). That auth constraint is operationally important and not derivable from annotations or schema. Missing only failure modes such as rate limits or behavior on unsupported platforms.

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 purpose before capabilities and prerequisites. No filler, though the phrasing is telegraphic and could tie the citation note more directly to the return value.

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 does its part by sketching the return shape and auth requirement, but for a paginated? no – it exposes limit and cursor in the schema yet the description says nothing about paging, defaults, or what happens when a platform is unavailable. Adequate rather than complete.

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 3 is the baseline, but the description adds real meaning by narrowing platform support to bluesky, hackernews, reddit and douyin. That clarification is useful because the schema's own platform description advertises ten platforms, five of which are absent from the enum – the description resolves which are actually live here.

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 the resource and the recency scope concretely: "What is popular on the platform right now." That distinguishes it from get_post/search_posts siblings by signaling ranked/popularity content rather than query-driven lookup, though it never names an alternative explicitly.

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 only implied by "right now" and "popular" – an agent can infer this is the discovery/trending entry point rather than targeted retrieval. There is no explicit when-not guidance or pointer to search_posts/get_user_posts for specific queries.

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