ga4_landing_pages

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

Annotations already mark the tool read-only, so the description correctly focuses on added behavioral detail: the join to Search Console and the path normalization rules (no host, no trailing slash, no query string). This goes beyond what the schema or annotations provide, though it does not discuss sampling or property selection.

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 dense, efficient sentences with no redundancy. The metric set and identity come first, and the path-normalization behavior earns its place as the key differentiator.

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?

With an output schema and read-only annotations, the description covers core identity and join behavior well. However, with five undocumented optional parameters, the agent is left guessing about filtering, date handling, and property selection, and the description does not guide away from siblings like ga4_run_report.

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% and all five parameters are undocumented. The description only mentions the output path key and never explains top_n, start_date, end_date, property_id, or path_contains, so it fails to add meaning beyond the schema.

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 concrete report — sessions, engagement rate, conversions, and revenue by landing page — and identifies it as the preset that joins to Search Console. It also distinguishes itself from gsc_search_analytics by explaining the shared normalized path key.

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 clearly implies this tool is for GA4 data joined with Search Console and that its path key is directly comparable to gsc_search_analytics rows. It stops short of explicitly naming sibling alternatives or saying when not to use it, but the join context is strong guidance.

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