zernio_get_linkedin_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. It does not disclose read-only behavior, authentication requirements, rate limits, or any side effects. It only lists the metrics returned without explaining operational characteristics.

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, front-loaded sentence that efficiently conveys the tool's action and output. It is concise and wastes no words, though it could benefit from a slightly more structured breakdown.

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 simple analytics tool with no output schema, the description adequately covers the what and the returned metrics. However, it does not disambiguate from similar siblings (e.g., zernio_get_post_analytics) or explain prerequisite steps like connecting LinkedIn accounts, leaving gaps for an agent.

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. The description adds no extra meaning beyond the schema: it does not explain the context of accountId, date range usage, or provide examples. The description fails to add value to parameter understanding.

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 the tool retrieves LinkedIn post-level analytics and lists specific metrics (impressions, clicks, likes, comments, shares, engagement). It effectively distinguishes from sibling tools like 'zernio_get_linkedin_analytics' by specifying 'per post', making the purpose unmistakable.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it or which sibling tools (e.g., zernio_get_linkedin_analytics or zernio_get_post_analytics) might be more appropriate for broader or different analytics needs.

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