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

With no annotations provided, the description carries the full disclosure burden. It usefully discloses that data is 'read live from the platform (TikTok so far)' and includes each platform's public URL, which tells the agent about data freshness and platform coverage. However, it omits auth/permission requirements, latency or rate-limit expectations, and behavior when a platform is unsupported.

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?

A single front-loaded sentence naming the returned fields and the data source; there is no redundant filler. It is slightly dense but every clause (metrics, per-platform, live, URL) adds information.

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 or annotations, the description does well to enumerate the returned metrics and mention the public URL, but it leaves gaps: the meaning of the required 'id' parameter, error/edge cases for unsupported platforms, and freshness caveats beyond 'live'. Adequate but incomplete for a tool with zero structured documentation.

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% for the single 'id' parameter, so the description must compensate, yet it never explains that 'id' identifies the post whose stats are fetched. The agent must infer the parameter's meaning from the tool name alone.

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 clearly conveys that this retrieves engagement metrics (views, likes, comments, shares) for a published post, which distinguishes it from the sibling get_post (which returns the post itself) and the mutation tools. It lacks an explicit verb+resource framing like 'Retrieve statistics for a post', but the intent is unambiguous.

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?

There is no explicit when-to-use guidance, no mention of alternatives such as get_post, and no stated prerequisites (e.g., the post must be published). Usage is only implied by 'How a published post is doing', leaving the agent to infer when this tool is appropriate.

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