ga4_landing_page_conversions

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false; the description adds behavioral details (sort order, default filter) beyond those annotations, with no contradictions.

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 sentences, zero waste: first sentence delivers core function and key details, second adds wrapper context. Every part is essential.

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 explains the tool's output (landing pages with conversions, breakdown, sort) adequately for a simple read-only tool with 100% schema-covered params. No output schema exists, but the description covers the basics; minor gap in explicit column listing.

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 100%, so the schema already documents all parameters. The description repeats default values that are also in schema, adding no new meaning beyond what the schema provides—baseline 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 the tool lists landing pages with conversions/key events, broken down by channel group, sorted descending, and defaults to organic search. It calls itself a 'convenience wrapper over ga4_run_report,' which distinguishes it from siblings like ga4_top_landing_pages or ga4_run_report.

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 implies use for SEO analysis by stating 'the SEO view' and default organic filtering. It provides context but does not explicitly state when not to use or compare to alternatives, though siblings hint at differences.

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