OpenPanel: Get top referrers

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

readOnlyHint=true already establishes that this is a safe read, so the description need not restate safety. Beyond that it says nothing about return shape, ordering, how many rows come back, or whether unauthenticated/unknown referrers are included, all of which matter for interpreting a ranking result.

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?

It is a single short sentence with no filler, but the '[UNIFIED]' tag is noise and the brevity comes at the cost of under-specification rather than efficiency.

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?

With four undocumented parameters, no output schema, and only readOnlyHint as annotation support, the definition leaves major gaps an agent would need filled before calling it correctly. A short clause on the required site, the date range format, and the ranked return would have closed most of them.

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% for four parameters (site, limit, date_range, project_id), so the description carries the full burden and adds essentially nothing. Only the word 'top' implicitly suggests ranking/limited results; the required site parameter, the date_range format, and the meaning of project_id are all left undocumented.

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 names a specific verb and resource: get top traffic sources/referrers, which is distinguishable from siblings like openpanel_get_top_pages or openpanel_get_geo_data. The '[UNIFIED]' prefix adds no informational value, and there is no explicit statement of how it differs from the other ranking 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?

There is no guidance on when to use this versus the other ranking/report tools, and no stated preconditions. 'via Insights API' hints at the data source but does not tell an agent when this tool is the right choice.

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