zernio_get_follower_analytics

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

With no annotations provided, the description carries full burden. It implies a read operation but does not disclose permissions needed, rate limits, default behavior when parameters are omitted, or whether the tool is read-only. Minimal behavioral context beyond the surface meaning.

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?

A single sentence of 14 words that conveys the essential purpose without fluff. Every word 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?

The description lacks specification of output structure (e.g., return format) and does not clarify which platforms/accounts this applies to. With no output schema, it should describe the return value shape. Adequate but not thorough.

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 schema already documents all parameters. The description adds no new meaning beyond hinting that dateFrom/to relate to time range, which is already in the schema. Baseline score of 3 applies.

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 verb 'get' and resource 'follower growth stats' with specific metrics (total, gained/lost, growth rate). However, without explicit differentiation from the similar sibling 'zernio_get_follower_stats', it loses one point for potential confusion.

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 mentions 'for a connected account', implying a prerequisite, but provides no guidance on when to choose this tool over alternatives (e.g., zernio_get_follower_stats, other analytics tools). No exclusions or when-not-to-use advice given.

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