Analytics: pagine di destinazione organiche

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

readOnlyHint already declares this as a safe read, so the description only needs to add context. It does add useful output content (sessions, engagement, conversions, revenue), but says nothing about scope limits, default rows, or behavior when dates are omitted despite the schema allowing defaults.

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 tight sentences: the first front-loads what the tool returns, the second adds the pairing rationale. Nothing is redundant, though the second sentence is slightly promotional rather than operational.

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 six optional parameters at 83% schema coverage, no output schema, and read-only annotations, the description covers what data comes back and roughly where it fits, which is close to sufficient; only the distinction from ga_report and the omitted-date default behavior are missing.

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 83%, so the schema already documents days, source, property, startDate and endDate. The description adds no parameter-level meaning (e.g., what 'organic' implies for the source filter), so the baseline of 3 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?

The description names a specific resource (pagine di destinazione del traffico da ricerca organica) and enumerates the metrics returned (sessioni, coinvolgimento, eventi chiave, ricavi), so an agent knows what it produces. It does not, however, explicitly distinguish it from the sibling ga_report, which is the nearest overlapping GA4 report tool.

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 line 'Si abbina bene a Search Console: le query portano clic, qui si vede cosa succede dopo' gives a genuine context-of-use cue for pairing with GSC tools, but there is no explicit when-to-use / when-not guidance and no comparison against ga_report or ga_compare_periods, so alternatives remain unaddressed.

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