ga4_gsc_content_roi

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

With no annotations, the description fully carries the burden of behavioral disclosure. It discloses data joining on normalized URLs, join rate variability (70-90%), potential mismatches due to timezone and sampling, and explicit instructions to report exact numbers and avoid speculation. This is detailed and actionable, going far beyond typical descriptions.

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 core value proposition, followed by essential requirements and caveats. Every sentence earns its place, and the structure flows logically from purpose to prerequisites to important usage rules. It is appropriately sized for the tool's complexity.

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?

For a complex tool with no output schema, the description gives strong operational context (how to handle data limitations and respond to queries). However, it does not describe the return format or how the 'diagnosis' is presented. This is a minor gap, as the agent could still use the tool effectively, but a clearer output description would improve completeness.

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?

All five parameters are fully described in the schema, so baseline is 3. The description adds no additional parameter-level detail (e.g., how days interacts with timezone caveats). It does not compensate for gaps because there are none, but it also doesn't enrich the meaning of any parameter.

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 a specific dual purpose: find pages that rank well but don't convert and pages that convert but rank low. It also says 'Diagnoses each page,' adding a distinct analysis scope. This differentiates it from GSC-only tools and GA4+GSC performance tools by focusing on the rank-conversion gap.

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 strong context for when to use the tool, including the requirement for GA4 BigQuery export and the insight that it helps decide between fixing the page vs investing in SEO. However, it does not explicitly mention alternatives or when not to use it, though the 'fix the page, not the SEO' framing implies the type of decision it supports.

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