zernio_get_post_analytics

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

With no annotations, the description must disclose behavioral traits, but it only lists metrics. It omits details on rate limits, data freshness, permissions required, or behavior when optional parameters (postId) are omitted. The tool is read-only but no indication of safety or potential side effects.

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 sentence clearly states the tool's purpose and the metrics retrieved. It is well-structured and easy to parse, though it could include more detail without being verbose.

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 absence of output schema and annotations, and the presence of 5 parameters (dateFrom, dateTo, platform, postId), the description is insufficient. It does not explain the optional parameters, date range semantics, or how the tool behaves when postId is missing. This leaves the agent with significant uncertainty.

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 100%, so the baseline is 3. The description adds context about the return metrics but does not clarify parameter usage or dependencies beyond what the schema provides. No contradiction, but limited added value.

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 clearly states it retrieves performance metrics including impressions, reach, likes, etc., for a specific post. However, the required parameter is only accountId, and postId is optional, which is inconsistent with 'specific post' and could cause confusion. The name distinguishes it from sibling analytics tools.

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 description provides no guidance on when to use this tool versus alternatives like get_follower_analytics, get_daily_metrics, or platform-specific analytics tools. No exclusions or context are given.

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