ga4_top_landing_pages

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

Annotations already declare readOnly, idempotent, not destructive. The description adds that it's a convenience wrapper but no additional behavioral traits (e.g., rate limits, pagination). With annotations covering safety, a 3 is appropriate.

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 concise sentences with no wasted words. First sentence covers purpose and metrics; second adds the key filter and wrapper context. Efficient and well-structured.

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?

Given the simple tool with 100% schema coverage and annotations, the description is fairly complete. It mentions returned metrics. Without an output schema, more detail on results would be helpful but not critical for this straightforward tool.

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 100% with each parameter documented. Description reinforces the organic_only default and the wrapper nature. Baseline 3 is correct when schema does the heavy lifting, and description adds limited extra meaning.

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 it returns top landing pages with sessions, engagement rate, and conversions over N days, defaulting to organic search. It distinguishes itself from ga4_run_report by being a convenience wrapper, and from other GA4 tools by its specific focus.

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 indicates when to use (SEO view, organic default) and that it's a wrapper over ga4_run_report, implying ga4_run_report for more flexibility. However, it doesn't explicitly exclude other siblings like ga4_organic_search_overview, which could overlap.

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