Get post metrics

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

Annotations already mark the tool as read-only and non-destructive, and the description adds substantial behavioral context: unsupported metrics are stored as 0 and must be reported as unavailable, platform-specific metric availability is detailed, linkClicks semantics are clarified, and bot traffic exclusion is mentioned. No contradiction with 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?

The description is long but dense with necessary caveats about platform-specific metrics and linkClicks semantics. It front-loads the core purpose and then explains behavioral nuances. Some sentences could be tightened, but the detail earns its place.

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 lack of an output schema and the complexity of the return data, the description explains key return fields, platform variations, zero-value semantics, and linkClicks handling. It does not fully describe the root response structure, but enough context is provided for correct invocation and interpretation.

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% for the single postId parameter, so the schema already documents it. The description adds context by referring to 'a published post,' but it does not further explain parameter format or edge cases. Baseline 3 is appropriate.

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?

Description clearly identifies the operation: getting engagement metrics for a published post and lists the returned metric types. It does not explicitly differentiate from siblings like get_post or get_analytics, but the 'use this when' clause gives a clear functional boundary.

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?

Explicitly states when to use the tool: 'Use this when the user asks how a specific post performed (likes, views, engagement).' It does not enumerate alternatives or exclusions, but the guidance is sufficient for a targeted metrics lookup.

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