website_stats

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It describes output (metrics with prior-period comparison) but fails to mention error handling, authentication requirements, rate limits, or that it is a read-only operation. The description adds minimal behavioral context beyond the schema.

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 efficiently conveys the tool's purpose and output, listing relevant metrics without extraneous information. It is well-structured and front-loaded.

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?

For a tool with 3 parameters and no output schema, the description provides a clear picture of what metrics are returned (pageviews, visitors, etc., with prior-period comparison). It is complete enough for a summary statistics tool, though the sibling set indicates more analytical tools exist. No output schema is needed given the description.

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%: each parameter has a clear description (e.g., 'Range end, ISO date. Optional; defaults to now.'). The description adds no additional semantics beyond the schema, so a baseline score of 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 states the tool provides 'summary metrics for one website over a date range' and lists specific metrics like pageviews, visitors, etc., with prior-period comparison. This verb+resource combination is specific and distinguishes it from siblings like 'pageviews_series' (time series) and 'metrics' (general), as well as exploration tools.

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 obtaining summary statistics over a date range but does not explicitly state when to use this tool versus alternatives like 'funnel_report' or 'retention_report'. No exclusions or comparative context is provided.

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