Get post analytics

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates that the tool returns metrics and gives example metric names; it does not reveal whether the data is cached or real-time, whether it triggers a refresh, what happens for invalid/missing post IDs, or any auth/rate-limit implications.

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 description is a single compact phrase with illustrative metric examples. Every word earns its place, and the core scope is front-loaded.

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 annotations and no output schema, the description should explain more about return shape and invocation context. It lists a few metrics but omits usage guidance, behavioral caveats, and parameter semantics, leaving an agent with only a minimal understanding of the tool.

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 compensate. It does not explain postId beyond the parameter name and the general 'one post' phrasing; there is no guidance on ID format, where to obtain it, or how it relates to connected accounts.

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 'One post's metrics (likes, comments, reach, …)' uses a specific verb-resource pairing and clearly scopes the tool to a single post. This distinguishes it from siblings like get_account_analytics and get_bulk_post_analytics without needing to open their schemas.

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?

'One post's metrics' clearly implies the tool is for retrieving analytics for a single post. However, it does not explicitly mention when not to use it or point to get_bulk_post_analytics/get_account_analytics as alternatives, so it stops just short of full guidance.

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