ga_send_pageview

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

The description adds the behavioral detail 'Automatically uses page_view event name', which is not in annotations. It also aligns with readOnlyHint=false as a write operation, but does not disclose other side effects such as property prerequisites or error behavior.

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 two sentences, with the primary action front-loaded and no fluff. Every word contributes to understanding the tool's purpose and behavior.

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?

The description is adequate for a simple pageview event sender, covering the core action and the automatic event name. However, it omits any mention of return values or required property configuration, which would be useful given there is no output schema.

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?

The schema already provides descriptions for all 6 parameters, achieving 100% coverage. The tool description adds no additional parameter-level semantics, so the baseline score of 3 is appropriate.

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 'Send a page view event to Google Analytics' and 'Standard event for tracking page/screen views', which both identifies the action and differentiates it from sibling tools like ga_send_purchase or ga_send_signup.

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?

It gives clear context that this is the standard tool for page/screen views, which is useful for selecting it among the sibling send tools. However, it does not explicitly state exclusions or name alternative tools for non-pageview events.

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