zernio_get_post_timeline

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a timeline of metrics evolution but does not specify response structure, time range, pagination, authentication needs, or error behavior. The examples (impressions, engagement) are helpful but insufficient for full transparency.

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 sentence that front-loads the main action and includes examples. It is concise with no wasted words, but could be slightly more structured (e.g., explicitly stating return type).

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 simplicity (2 params, no output schema, no annotations), the description covers the basic functionality and example outputs. However, it lacks details on return format, time range handling, and potential limitations. It is adequate but not fully complete.

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% with minimal descriptions ('The Zernio account ID' and 'The post ID to get the timeline for'). The tool description adds context about the tool's purpose but does not enhance understanding of the parameters beyond what the schema already provides. 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?

The description clearly identifies the verb ('Get') and resource ('a post's performance over time as a timeline'), specifies example metrics ('impressions and engagement'), and mentions granularity ('hour by hour or day by day'). This distinguishes it from siblings like 'zernio_get_post_analytics' (likely overall stats) and 'zernio_get_post' (post details).

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 implies usage for post-publishing performance tracking but does not explicitly state when to use it versus alternatives like 'zernio_get_post_analytics' or 'zernio_get_daily_metrics'. No when-not-to-use or prerequisite information is provided.

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