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

With no annotations, the description carries the full burden for behavioral disclosure, but it only describes the returned data (active visitors, current page/path). It does not mention whether visitors are unique, pagination, authentication requirements, or any rate limits, leaving the agent to guess about side effects and 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?

A single efficient sentence with no filler; every word contributes to the core meaning. The key qualifier 'last 5 minutes' is placed near the start.

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 one-parameter tool, the description covers the basic purpose and returned fields, but the undocumented 'site' parameter and lack of any output structure leave gaps. The absence of annotations also means nothing discloses read-only behavior, though the name 'get_realtime' implies it.

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?

The schema provides only a required string named 'site' with 0% description coverage, so the description must explain how to populate it. The phrase 'on the site' weakly suggests that the parameter refers to the site identifier, but it does not specify format, accepted values, or how it maps to a site ID/domain.

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 identifies the resource (visitors active on the site) and a specific time window (last 5 minutes), which distinguishes it from the broader get_visitors sibling. It lacks an explicit verb like 'Returns' or 'Gets,' but the meaning is clear.

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?

No guidance is given on when to choose this tool over get_visitors, get_stats, or get_timeseries. The 'last 5 minutes' qualifier implies a real-time use case, but no alternatives, exclusions, or prerequisites are stated.

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