pirsch_active

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

With no annotations provided, the description carries the full burden. It explains the time window and what is retrieved (active visitors and pages), but it does not disclose potential rate limits, authentication requirements, or whether the data is approximate or exact. This is adequate but lacks extra behavioral context.

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, efficient sentence that front-loads the key action and resource. Every word contributes meaning, with no redundancy or filler.

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 has 2 parameters (none required), no output schema, and no annotations, the description covers the basic purpose and time window. However, it lacks details on the meaning of 'active', the exact output format, and any pagination or limits. This is adequate but not fully complete for an agent to invoke without further inference.

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 0%, so the description must compensate. It specifies a default of 600 seconds for the time window, implying the 'start' parameter is a number of seconds, but it does not clarify if 'start' is a timestamp or offset. The 'domain_id' parameter is not explained. The description adds some meaning but leaves ambiguity for both parameters.

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 'active visitors and pages', with a specific time context 'past N seconds (default 600)'. This distinguishes it from sibling tools like pirsch_visitors and pirsch_pages, which likely return all data rather than active data.

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 by mentioning 'past N seconds' and a default value, but it does not explicitly state when to use this tool versus alternatives like pirsch_visitors or pirsch_pages. No exclusion criteria or alternative recommendations are provided.

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