Get post analytics

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

Annotations already cover the read-only and non-destructive nature. The description adds value beyond annotations by disclosing that post_metrics is not a fixed shape, may differ by platform, and enumerates the TikTok-specific extras. This is above-average behavioral context, though it doesn't cover platform absence behavior or response edge cases.

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?

The first sentence front-loads the main purpose, and the second sentence expands on the non-standard output shape. The TikTok field list is long but relevant to prevent an agent from expecting a fixed schema; still, it could be tightened without losing that insight.

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?

Given the presence of an output schema and annotations, the description covers the key non-obvious point: results differ per platform. It also gives a concrete example of the extra fields. It doesn't explain which platforms are supported or how the request_id originates, but those are not critical for invoking the tool correctly.

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?

With 0% schema coverage, the description helps by identifying the single parameter as the post identifier. However, it writes the parameter as `request_id` while the schema expects `requestId`, which is a small but real invocation risk. It doesn't explain where to obtain the request ID, so the semantic help is partial.

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 the resource clearly: per-platform metrics for a specific post identified by a request ID. It distinguishes from general analytics by being post- and platform-specific, but it does not explicitly differentiate itself from close siblings like get_cached_post_analytics or get_platform_metrics.

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 implied usage is clear: call this when you need per-platform metrics for one post. However, there is no explicit when-not-to-use guidance or mention of alternatives, so the agent has to infer boundaries from the parameter and sibling list.

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