run_realtime_report

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It does add the key time window ('last ~30 minutes'), but it does not mention expected permissions, response format, or error handling. As a read-only report operation, the safety profile is implied but not explicitly stated.

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 a single, front-loaded sentence with a helpful example. Every word earns its place; there is no redundancy or filler.

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 tool with 4 parameters, no annotations, and no output schema, the description is notably incomplete. It omits details about response structure, valid metric/dimension formats, and any limitations. The example gives a hint, but an agent would need more guidance to invoke this tool reliably.

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 0%, so the description must compensate. It provides a concrete example with metrics and dimensions, giving some context for their usage, but it leaves limit and property_id unexplained. The example helps but is not enough to fully clarify parameter semantics.

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 tool's purpose: 'Run a GA4 realtime report (last ~30 minutes).' The verb is specific, the resource is a GA4 realtime report, and the time window distinguishes it from sibling tools like run_report. An example further clarifies the expected usage.

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 implies when to use this tool via the phrase 'last ~30 minutes', but it does not explicitly state how it differs from alternatives like run_report, nor does it provide any when-not-to-use guidance. The context is there, but exclusions are absent.

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