zernio_get_daily_metrics

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 indicates a read operation and lists return fields, but it does not disclose behavioral traits such as pagination, rate limits, data freshness, or whether the metrics cover all platforms. The description is minimal.

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, concise sentence that is front-loaded with the action and resource. It efficiently conveys the tool's purpose without wordiness.

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 lists the returned metrics, which is helpful since there is no output schema. However, it lacks details on metric definitions, date range behavior, or platform filtering nuances. For a tool with 4 parameters and no output schema, it is adequately but not thoroughly 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 description coverage is 100%, so the baseline is 3. The description does not add additional meaning beyond what the schema provides for parameters like accountId, dateFrom, dateTo, and platform. The schema already has descriptions for each parameter.

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 verb 'Get', the resource 'day-by-day account metrics', and lists specific metrics (impressions, reach, engagement rate, etc.). It distinguishes from sibling tools by focusing on daily account-level data.

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 retrieving daily account metrics but does not explicitly state when to use this tool over alternatives like platform-specific analytics tools (e.g., zernio_get_instagram_insights) or other account-level tools. No when-not or alternative tool guidance is provided.

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