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

Annotations already establish safe read-only, idempotent behavior, so the description's added value is in disclosing the payload: a 5-minute activity window, a 30-minute per-minute series, and latest events/payments. Useful disclosure beyond structured fields, though nothing about freshness/refresh cadence or result size limits.

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-loads the data it returns, then ends with a usage cue in a single compact sentence. The enumeration is dense but each clause maps to a distinct part of the payload, so it earns its space.

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?

There is no output schema, so the description carries the burden of describing return contents — and it does, covering both the visitor list and the minute-level series. Minor gaps: no note on result volume or how fresh the data is.

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?

Only one parameter (site) and schema description coverage is 100%, so the schema already explains domain/id/public-id formats and optionality. The description adds no parameter guidance of its own, which is acceptable but not value-adding.

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?

Names the exact resource and time window ('People active in the last 5 minutes') and enumerates the returned data (page, source, place, goals, customer status, visitors per minute, events, payments). This level of specificity clearly distinguishes it from aggregate siblings like get_overview or get_timeseries.

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?

Explicitly routes the agent with 'Use it for what is happening right now?', which sets the recency condition that separates it from historical/overview tools. It stops short of naming a specific alternative sibling or stating when not to use it.

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