Landing page analysis

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a preview of what is computed (sessions, conversion rates, bounce rates, engagement, zero-conversion pages, orphaned URLs), but says nothing about auth requirements, rate limits, or data latency, and much of the return content is already available in the output schema.

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 front-loaded sentences with no filler, stating purpose before output. The trailing API documentation links are somewhat verbose but plausibly useful, keeping this just short of maximum.

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 4 optional parameters at 100% schema coverage, an output schema, and clear annotations, the definition gives the agent enough to invoke the tool. The only meaningful gap is the absence of routing guidance against sibling reporting tools, which belongs to usage rather than 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?

Schema coverage is 100%, so customer_id, property_id, and both date fields are fully documented in the schema itself, including defaults and the 'both dates or last 30 days' rule. The description adds no parameter meaning beyond that, so the baseline of 3 for schema-driven documentation applies.

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?

States a specific resource and analysis goal ('which landing pages convert and which don't') and clarifies the method by naming the two data sources it joins (ad final URLs + GA4 page-level data). It is distinguishable from generic siblings like run_ga4_report by describing the cross-source join, though it never explicitly names a sibling it is not.

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 explains what the tool does but gives no when-to-use or when-not guidance and names no alternatives, despite sitting alongside closely related tools like run_ga4_report, get_campaign_performance, and analyze_page_speed. An agent must infer the selection conditions from the output description alone.

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