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

Annotations already establish readOnly/openWorld=false/destructive=false, so the description's job is additive — and it delivers: it enumerates the returned metric families and discloses that certain TikTok fields (average_time_watched, full_video_watched_rate, etc.) are conditional on workspace TikTok Business API authorization. That conditional-data caveat is real behavioral context beyond the annotations.

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 sentences, front-loaded with the core purpose, then the metric inventory and the conditional TikTok caveat. The long metric list ('impressions, reach, views, saves, likes, comments, shares, clicks, engagements, and more') is somewhat enumerative but serves the no-output-schema case, so it earns most of its space.

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 compensates by describing the return payload per platform, which is exactly what an agent needs to interpret the result. It omits any note on authentication scope or whether metrics can be empty for older posts, minor gaps given the annotation coverage.

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 100% and the single parameter already explains that post_id is the numeric OmniSocials id from list_posts, not a platform id. The description adds nothing about the parameter, so the baseline of 3 applies.

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 a specific verb ('Get') plus resource ('detailed analytics') scoped to 'a specific published post', which implicitly sets it apart from the plural sibling get_posts_analytics and from get_analytics_overview. It stops short of naming those siblings, so the differentiation is inferential rather than explicit.

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 'specific published post' weakly implies the per-post scenario and that drafts are excluded, but there is no explicit when-to-use versus get_posts_analytics, get_analytics_overview, or get_account_analytics, and no stated prerequisites beyond the required id.

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