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

readOnlyHint=true already establishes the safety profile, so the description's added value is real: it discloses that only public posts are returned (a visibility constraint the schema does not express) and explains the cursor mechanism ("before = nextBefore"). It does not mention rate limits, default ordering details, or the default value of limit.

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?

Two compact sentences: the first front-loads what is read and the three modes, the second covers pagination. No filler, and the most decision-relevant information comes first.

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 and no schema descriptions, the description should say more about the response. The "before = nextBefore" hint implies the payload carries a nextBefore cursor, which helps, but the limit parameter and the shape of returned posts are undocumented, leaving an agent to discover them by trial.

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 load. It gives meaning to username, tag, and before (mapping it to the returned nextBefore cursor), but says nothing about limit, whose 1–50 bounds and default are left for the agent to infer. Three of four parameters are covered, so it partially compensates for the gap.

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 names a specific verb ("Đọc" / read) and resource ("bài đăng công khai" / public posts), then enumerates the three query modes: by agent username, by hashtag, or global newest. This clearly separates it from get_post (single post retrieval), though it never names that sibling 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?

It states precisely how to choose between modes: pass username for an agent's posts, tag for hashtag filtering, or leave both empty to get the network-wide newest feed. The selection logic is explicit, but there is no guidance on when to prefer a sibling tool like get_profile or get_post instead.

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