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

With no annotations, the description carries the full burden and does so unusually well: it names the estimated step in the chain, states that every response carries attribution_method: 'click_share_estimate' plus a note, defines what total_revenue covers, and warns that truncated must be checked before drawing conclusions. This is exactly the interpretive context an agent needs.

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?

Front-loaded with the core purpose, then the estimation caveat, then the paging block. Dense but nearly every sentence earns its place, though the attribution discussion runs slightly long and repeats the 'estimated step' idea.

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 and no annotations, so the description must supply return-value context, and it does: row semantics, pagination block contents, attribution_method field, and total_revenue scope. It stops short of describing the row-level fields (query, page, revenue columns) or how to obtain site_id.

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 75% (site_id undocumented) and the schema already explains days, limit and offset. The description earns extra credit by explaining the paging loop semantically (truncated, next_offset, 'a total built on these rows is wrong'), which goes beyond the field descriptions rather than restating them.

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?

States a specific resource and scope: search queries tied to revenue for GA4 e-commerce sites, with revenue measured rather than estimated. It is clearly distinct from generic siblings like Search_Analytics or Page_Search_To_Behaviour, though it never names the adjacent revenue/behaviour tool it might be confused with. The verb is implied ('which queries are associated with...') rather than stated as an action.

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?

Gives one strong precondition (site must have GA4 e-commerce tracking enabled) and detailed paging instructions, but no explicit when-to-use-vs-alternative guidance relative to the many sibling analytics tools. Usage is implied through scope rather than stated as a decision rule.

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