get_realtime_visitors

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

The description discloses the real-time nature and 5-minute window, but with no annotations, it carries the full burden. It does not clarify if the count is unique visitors or sessions, nor mention any other behavioral traits like response format or aggregation.

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 concise sentence that immediately conveys the purpose and key detail (real-time, last 5 minutes). No redundant information, perfectly front-loaded.

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?

Given the simplicity (1 parameter, no output schema), the description is largely complete. It explains the output (number of people) and time window. Minor detail missing: whether the count is unique visitors or sessions, but not critical.

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 coverage is 100% for the single parameter site_id, which already has a description. The tool description does not add any extra parameter meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 it retrieves the number of people currently on the site within the last 5 minutes, using a specific verb and resource. It distinguishes well from siblings like get_stats and get_timeseries by emphasizing real-time visitor count.

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 real-time usage but provides no explicit guidance on when to use this tool versus alternatives (e.g., get_timeseries for historical data). No exclusions or conditions noted.

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