Get Real-time Visitor Map

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

No annotations are provided, so the description must disclose behavior. It does mention included data types (events, payments, conversion predictions) but omits important behavioral details such as the time window for 'recent', whether coordinates are precise or anonymized, and if any rate limits or permissions apply. The read-only nature is implied by 'get' but not stated.

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 two sentences with no filler. The first sentence clearly identifies the tool's purpose, and the second adds useful context about included data. It is appropriately sized.

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 no output schema and no parameters, the description is the sole guide to expected data. It gives a high-level overview of return contents but lacks structural details (e.g., coordinate format, field names, response envelope). Given the simple no-parameter nature, it is adequate but could be more informative.

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 tool has zero parameters, and the schema covers 100% of the (empty) parameter set. Consequently, the description doesn't need to add parameter details, and the baseline of 4 applies.

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?

Clearly states the tool retrieves real-time visitor data with geographic coordinates specifically for map visualization, listing additional context (recent events, payments, predictions). This distinguishes it from sibling tools like get_realtime (which lacks geographic focus) and get_countries/get_cities (which are likely aggregated rather than real-time).

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?

Description implies usage for real-time location-based map views but doesn't explicitly mention when not to use it or alternatives. It doesn't say 'for non-geographic real-time data use get_realtime' or similar, so guidance is implicit rather than explicit.

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