get_top_referrers

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

Annotations already indicate readOnlyHint (true), destructiveHint (false), and idempotentHint (true). The description adds behavioral context: it returns hostnames by event count, supports AND filters, and has default date ranges. This provides useful detail beyond annotations without contradiction.

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 front-loaded with the primary purpose in the first sentence. It then efficiently covers filter syntax, date range options, and scoping. While it is moderately detailed due to the complexity of filters, every sentence serves a purpose and there is no redundancy.

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?

Given the tool's complexity (filters, date ranges, defaults, scoping), the description thoroughly covers all aspects: purpose, filtering options, date range presets and custom ranges, site scoping, and default limit. Since an output schema exists, the lack of return value explanation is acceptable, making the description highly 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 coverage is 100%, so the schema fully documents each parameter. The description adds meaning beyond the schema by explaining how filters work (AND together), how date ranges default per tool, and how site_id scopes the query. This extra context is valuable for correct usage.

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 retrieves 'top referrer hostnames by event count', which is a specific verb and resource. It distinguishes from siblings like 'get_top_pages' by focusing on referrer hostnames. The mention of filters and site scoping further clarifies the purpose.

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 provides clear context for when to use the tool: to get top referrers with optional filters and site scoping. It mentions passing site_id to scope to one site and supports date ranges. While it does not explicitly state when not to use or list alternatives, the purpose is distinct enough among siblings.

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