get_active

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description 'Current active visitors' gives no insight into behavioral traits such as whether this is a read-only operation, what permissions might be required, how data is returned (e.g., format, pagination), or any rate limits. It fails to provide any meaningful context beyond the basic purpose.

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 extremely concise with just three words, making it front-loaded and free of unnecessary details. However, this brevity borders on under-specification, as it sacrifices clarity and completeness for conciseness. Every word earns its place, but more content is needed to be helpful.

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 tool's complexity (a data retrieval tool with one parameter) and the presence of an output schema (which might cover return values), the description is incomplete. It lacks purpose clarity, usage guidelines, parameter semantics, and behavioral transparency. While the output schema could mitigate some gaps, the description fails to provide enough context for the agent to understand when and how to use this tool effectively compared to siblings.

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 one parameter (website_id) with 0% description coverage in the schema itself. The tool description 'Current active visitors' adds no information about this parameter—it doesn't explain what website_id represents, how to obtain it, or its role in filtering results. With low schema coverage and no compensation in the description, this leaves the parameter's meaning entirely undocumented.

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 'Current active visitors' restates the tool name 'get_active' in different words, making it tautological. It doesn't specify what action the tool performs (e.g., 'retrieve', 'fetch', 'list') or what resource it operates on beyond the vague 'visitors'. While it implies reading visitor data, it lacks the specific verb+resource clarity needed to distinguish it from sibling tools like get_metrics or get_pageviews.

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 provides no guidance on when to use this tool versus alternatives like get_metrics, get_pageviews, get_stats, or get_websites. It doesn't mention any context, prerequisites, or exclusions for usage. This leaves the agent with no information to make an informed choice among the available sibling tools.

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