Get Post Insights

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The parenthetical adds genuinely new information about the default metric set (reactions by type and clicks), but nothing about permissions, rate limits, or what happens with invalid/foreign post ids.

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 front-loaded sentence with zero filler; the default-metrics note is placed where it is immediately useful. Its brevity is efficient, though it borders on under-specification rather than being optimally sized.

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?

The tool is simple (3 params, full schema coverage, output schema present, so return values need no explanation), and the default metrics disclosure covers the main ambiguity. What is missing is routing against get_page_insights and any note on the page parameter's defaulting when the post belongs to another Page.

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 coverage is 100%, so the baseline is 3, and the description earns an upgrade by revealing what the 'defaults' actually are for the metrics parameter — information the schema only gestures at with 'Omit to use the defaults'. It still says nothing about valid metric names or the page parameter's resolution rules beyond the schema.

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 and resource ('Get analytics for one post') and scopes it to a single post, which distinguishes it from list-level siblings. It does not name or contrast with get_page_insights, the closest alternative, so the agent must infer the post-vs-page 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 explicit when-to-use guidance and no mention of the obvious alternative, get_page_insights, or of get_post/list_posts as prerequisites for obtaining a post_id. Usage is only implied by the phrase 'for one post'.

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