get_ga4_ai_referrers

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

No annotations exist. The description provides no behavioral details (e.g., read-only, scoping, or limitations) beyond stating the data returned.

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?

Single sentence conveys the core purpose efficiently with 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?

No output schema. Description fails to specify return format, scoping (e.g., property, date range), or list of engines, leaving significant ambiguity for a tool with no parameters.

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?

Input schema has no parameters (additionalProperties: true), so schema coverage is 100%. The description adds minimal value by indicating the data type but does not explain implicit filters or defaults.

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 explicitly states the tool retrieves AI/LLM referral traffic by specific engines (ChatGPT, Perplexity, etc.), clearly distinguishing it from sibling tools like get_ga4_summary or get_ga4_traffic_by_source.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or context-specific usage.

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