zernio_get_content_decay

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

The description reveals that the tool tracks performance drop-off over time, implying time-series data. However, it does not specify what data is returned when postId is omitted, nor does it mention authentication, rate limits, or data recency. Without annotations, more behavioral context would be beneficial.

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 is clear and front-loaded. However, the phrase 'see how reach and engagement drop off after publishing' is slightly redundant with the first part, but overall efficient.

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 no output schema, the description hints at return values (reach and engagement over time) but lacks specifics on format (e.g., time intervals, absolute vs relative changes). It is adequate for a simple analytics tool 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 descriptions for both parameters. The description adds minimal extra meaning beyond the schema, simply reinforcing the decay context. Baseline score of 3 applies since schema already documents parameters adequately.

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 tracks decay of post performance over time, focusing on reach and engagement. It distinguishes from generic analytics tools like zernio_get_post_analytics, but could be more precise about the type of decay data returned.

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 on when to use this tool vs alternatives such as zernio_get_post_analytics or zernio_get_daily_metrics. No prerequisites or context for usage are provided.

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