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

The description adds a genuine behavioral note not present in structured fields: PII is hashed for privacy, which tells the agent return values are masked. However, it omits the most consequential behavior — that this is a long-poll that blocks until events arrive or the wait window expires — and does not explain why readOnlyHint is false for a "get" operation.

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 short sentences with the core purpose front-loaded and no wasted wording. The trade-off is that the brevity comes at the cost of under-specification rather than through efficient information density.

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 nine parameters, two enums, no output schema, and streaming/long-poll semantics, the description is far too thin. It never explains what one call returns, how wait_for_events and max_wait_seconds shape the response, or that the call can block for up to 120 seconds.

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 67%, so the schema already documents most parameters, giving a baseline of 3. The description adds a small amount by framing the tool as spanning sources, destinations, and transformations, which motivates the three respective ID filters, but it adds no detail on event_name, event_type, or filtering 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?

States a specific verb and resource: get real-time events, scoped across sources, destinations, and transformations. This distinguishes it reasonably from metric-oriented siblings like get_destination_event_metrics, but it never explicitly names when to prefer it or why it differs from other event-listing tools.

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?

There is no when-to-use guidance, no prerequisites, and no named alternatives among the many sibling tools. The only implied usage comes from the parameter names, leaving the agent to infer that this is a live-tail/polling call rather than a historical query.

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