Get post analytics

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only a partial list of returned metrics; it says nothing about freshness/lag of analytics, supported platforms, time-window behavior, or permissions, which are the real unknowns for an open-world analytics read.

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?

It is front-loaded and wastes nothing, but at a single sentence fragment it reads as under-specification rather than disciplined brevity. Nothing in it could be cut, but much is missing.

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?

For a one-parameter read tool with no output schema, the description is at the edge of adequacy: it names the return content, which is the main thing the missing output schema would have covered. It still omits ID format, metric time window, and platform scope, which an agent needs before calling.

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 postId parameter, so the description carries the full burden — yet it only implies 'a post' without specifying the ID format (internal platform ID vs. this API's ID) or whether cross-account IDs are valid. That ambiguity will cause failed invocations.

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?

It states the resource precisely — metrics for a single post — and parenthetically names the metric families (likes, comments, reach). It does not use a verb or explicitly contrast itself with the obvious sibling get_bulk_post_analytics, so the agent must infer the single-vs-bulk split.

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 when-to-use guidance, no prerequisites, and no mention of the alternative bulk or account-level analytics tools in the sibling list. The word 'One' hints at single-post scope but the routing decision is left entirely to inference.

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