Get Visitor Details

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses what information the tool returns (identity, activity, conversion predictions), which is useful, but it does not mention side effects (though 'Get' implies read-only), authentication needs, error behavior for missing visitor, or rate limits. Partial transparency.

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, well-structured sentence that packs all relevant information without superfluous words. It is front-loaded with the core purpose and lists the key data categories efficiently.

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 tool with one parameter and no output schema, the description adequately covers the purpose and the return content categories. It lacks edge-case details like error handling or data freshness, but these are less critical given the low complexity, making it nearly complete.

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 description coverage is 100% with the visitorId parameter described as 'The DataFast visitor ID'. The tool description adds no additional meaning beyond what the schema already provides, so baseline 3 is appropriate; it does not clarify format, constraints, or usage nuances.

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 the verb 'Get' and the resource 'specific visitor', and enumerates the exact categories of information returned (identity, activity, conversion predictions). This distinguishes it from sibling tools like get_overview or get_pages which operate on aggregate or different resources.

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 usage when you need details on a specific visitor by mentioning 'specific visitor' and requiring a visitorId parameter. However, it gives no explicit when-to-use vs alternatives, no exclusions, and no guidance on when not to use this tool, leaving usage context mostly inferred.

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