ga4_run_report

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

With no annotations, the description bears the full burden but adds little beyond purpose. The metadata prerequisite is a useful behavioral hint, but it doesn't disclose output format, error behavior, or rate limits. The term 'report' implies read-only, but this isn't explicit.

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 consists of two sentences: one for purpose and one for the key prerequisite. It is front-loaded, concise, and every sentence earns its place with no redundancy.

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 tool has 10 parameters and no annotations, but the schema provides rich parameter descriptions. The description covers basic purpose and metadata discovery but omits when to use simpler predefined reports and lacks return value context. It is minimally adequate but not fully complete for a complex tool.

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 baseline is 3. The description adds value by telling the agent to use ga4_get_metadata to discover valid dimension and metric names, which is essential for correct parameter usage. This goes beyond the schema's static examples.

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 'Run a custom GA4 report' with a specific verb and resource. It distinguishes from siblings like ga4_top_pages and ga4_realtime_report by emphasizing 'custom' and flexible dimensions/metrics/date ranges.

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 clear usage context by instructing to 'Use ga4_get_metadata to discover available dimensions and metrics first,' which sets a prerequisite and points to a sibling tool. It implies this is for custom reports but doesn't explicitly list exclusions or alternative tools, so it's clear but not exhaustive.

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