analytics_organic_landing_pages

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

With no annotations provided, the description must fully disclose behavioral traits. It only states that the tool retrieves data and that it matches GSC data, but it does not address important behaviors such as data range limits, required permissions, rate limits, or whether the operation is read-only. The description conveys a read operation, but lacks details that would help an agent anticipate side effects or constraints.

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?

The description is concise, comprising a single sentence that is front-loaded with the verb and resource. It efficiently communicates the core purpose. However, given the brevity, some important details are omitted, but that is a matter of completeness rather than conciseness. The structure is clean and easy to parse.

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?

Despite having 6 parameters and 3 required fields, the description is very brief and does not explain the return format, what 'performance' means (e.g., metrics like clicks, impressions, etc.), or how the data matches GSC data. It also does not address the multi-account setup indicated by the 'accountId' parameter. The lack of output schema further increases the need for description completeness, which is not met.

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%, meaning each parameter already has a description in the input schema. The tool description adds the contextual note 'matches GSC data', which provides a hint about data consistency but does not elaborate on parameter usage or format beyond the schema. According to guidelines, baseline is 3 when coverage is high, and this description meets that baseline without adding much value.

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 verb 'Get' and the resource 'performance of organic landing pages in GA4'. It also provides the distinguishing feature 'matches GSC data', which helps differentiate it from siblings like 'analytics_top_pages' or 'bing_get_top_pages'. However, it does not specify which performance metrics are included, which is a minor gap.

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 provides no explicit guidance on when to use this tool versus alternatives. The only hint is 'matches GSC data', which implicitly suggests it is for cross-referencing with Search Console, but it does not clearly state use cases, prerequisites, or when not to use it. For example, it does not contrast with other analytics tools that might serve similar purposes.

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