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

With no annotations present, the description carries the behavioral burden. It discloses that results are daily series, which metrics are included, and that dates align with the site's timezone. This is meaningful behavioral context beyond the schema, though it does not address response shape, date-window defaults, or limits.

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 compact sentence that front-loads the core purpose and packs the metrics and timezone detail into a parenthetical. Every word adds value, and there is no redundancy or fluff.

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 tool has four parameters, no parameter descriptions, no output schema, and no usage/alternative guidance. The description explains what data is returned but omits how to specify the requested date range and what the response looks like, so an agent cannot invoke it with full confidence.

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 0%, so the description must clarify parameter meaning, but it only loosely supports the 'site' parameter with 'for a site.' The date-related parameters to, days, and from are completely unexplained, leaving their formats, precedence, and interactions ambiguous.

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 a daily traffic series for a site and lists the included metrics: visits, visitors, pageviews, clicks, and bots. It is set apart from siblings like get_realtime and get_breakdown by emphasizing daily granularity, though it lacks an explicit verb and does not directly name a differentiating sibling.

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 use for daily aggregated site traffic in the site's timezone, which helps an agent distinguish it from real-time or breakdown tools. However, it provides no explicit guidance on when to choose this tool over get_stats, get_visitors, get_breakdown, or get_bot_report, and no exclusions are stated.

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