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

No annotations are provided, so the description carries the full burden. It does disclose the 5-minute window and the returned fields (current page, path), but it does not explicitly say the operation is read-only, nor mention edge cases such as empty results, pagination, or rate 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?

The description is a single concise sentence with no filler. The key constraint (last 5 minutes) is front-loaded, and every word contributes to understanding the tool.

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 simple one-parameter read tool, the description covers the core concept, but it lacks output structure details and clear parameter value guidance. The presence of similar sibling tools like get_visitors also makes the missing differentiation more noticeable.

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 input schema has 0% description coverage and only defines 'site' as a string. The description merely says 'on the site,' which gives some context but fails to clarify whether the value should be a site ID, domain name, or slug, leaving the parameter semantics under-specified.

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 identifies what the tool returns: visitors active in the last 5 minutes with their current page and path. It is specific and distinct from siblings like get_visitors or get_timeseries, though it lacks an explicit verb such as 'Retrieve'.

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 phrase 'in the last 5 minutes' implies this is for real-time visitor data, which is a usage context. However, there is no explicit guidance on when to use this tool versus alternatives like get_visitors, and no exclusions or conditions are stated.

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