get_revenue_insights

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

No annotations are provided, so the description carries the full burden, and it delivers two meaningful behavioral facts: 'read-only' and 'Credits: 0'. It also explains the has_data=false edge case (nothing is estimated yet), which prevents misreading an empty result as zero revenue. It omits auth/permission or rate-limit details, so it is strong but not exhaustive.

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?

Two short lines with zero filler, front-loaded with the resource and its outputs, followed by cost and the has_data caveat. Information is well ordered and every clause earns its place. It is slightly clipped rather than fully polished prose.

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?

An output schema exists, so the description need not document return shape, and it still flags the has_data edge case. It covers cost, safety posture, and scope. The remaining gap is the absence of any usage routing among the many sibling analytics tools, which keeps it from a 5.

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%, but there is only one required parameter (project_id), whose meaning is self-evident from its name and type. The description adds no scoping or format detail for it. For a single obvious identifier parameter, 3 reflects adequate-but-unelaborated semantics.

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 resource and scope ('Organic revenue attribution') and enumerates the concrete outputs the tool returns (totals, top keywords/landing pages, Pareto, cluster revenue), so an agent knows exactly what it produces. It doesn't explicitly contrast itself with nearby siblings like get_analytics_insights or get_traffic_snapshot, so it stops short of a 5.

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 when-to-use guidance and no named alternative, despite a crowded sibling space with several analytics/reporting tools. The only conditional stated is about the has_data return flag, which is data semantics rather than usage routing. An agent gets no help deciding between this and get_analytics_insights.

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