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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds valuable behavior the schema can't express: metrics are fetched live at call time, platform coverage is currently limited to TikTok, and public URLs are included — all of which affect expectations about freshness and completeness.

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?

One tight sentence that leads with what the caller gets and follows with the important qualifier about live TikTok data. No filler or restated boilerplate.

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 enumerates the returned fields and the URL inclusion, which covers most of the return contract. However, it leaves the sole parameter ambiguous and says nothing about error behavior for unknown or unpublished ids.

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?

The single parameter 'id' has 0% schema description coverage, so the description needs to carry the burden and does not. It only indirectly implies the id identifies a published post; it never states the id format, whether it is the internal post id or a per-platform id, or what happens if the post is unpublished.

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?

Names the resource (a published post) and the exact payload (views, likes, comments, shares per platform plus public URLs), which is far more specific than a bare 'get stats'. It implicitly separates itself from get_post by emphasizing engagement metrics, 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?

The phrase 'published post' and 'read live from the platform' implies the tool only applies to already-published posts, which is useful context. But there is no explicit when-to-use guidance, no mention of what to do for unpublished/draft posts, and no routing to get_post or list_posts.

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