Analytics: report

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

Beyond the readOnlyHint annotation, the description discloses the ~1-day data freshness lag, which is a real behavioral trait an agent needs to avoid misreporting 'today's' numbers. It omits rate limits and default-property fallback behavior, so it is useful but not complete.

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?

Front-loaded with the core purpose, followed by the freshness caveat, then the value lists. The dimension/metric enumerations are long but earn their place by supplying otherwise-missing allowed values.

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?

For a 9-parameter, zero-required tool with no output schema, the description covers purpose, data lag, and the free-form array values that the schema under-documents. Filters, limit, and pagination are left to the schema but remain in Italian and self-describing, so nothing critical is 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 coverage is 67%, and the schema leaves 'dimensions' and 'metrics' as bare string arrays with no enumerated allowed values. The description compensates by listing valid dimensions and metrics, which materially improves correct invocation beyond the schema itself.

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 verb and resource ('Report libero su Google Analytics 4') with scope modifiers ('dimensioni, metriche e filtri a scelta'). An agent can tell this is the flexible/generic GA query tool distinct from ga_organic_landing_pages or ga_realtime, though no sibling is named explicitly.

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?

Usage is implied rather than stated: 'filtri a scelta' signals this is the build-your-own query tool, and the dimension/metric lists hint at valid usage. There is no explicit when-to-use-this-vs-ga_compare_periods or ga_organic_landing_pages guidance and no exclusions.

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