pirsch_pages

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

With no annotations, the description must reveal behavioral traits. It only mentions sorting/search/avg time but omits that it's a read operation, any default behavior, pagination, or what happens with empty results. The large schema suggests extensive filtering capability, but that is not disclosed.

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 short sentence, which is front-loaded with 'Get page stats'. However, given the tool's complexity (46 parameters), it is overly terse and sacrifices necessary detail for brevity.

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?

The tool has 46 parameters, no output schema, no annotations, and many sibling tools. The description provides almost no context: what the output looks like, default sorting/filtering, how to combine parameters, or which sibling to use when. This is completely inadequate for effective usage.

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 only 22%, meaning most of the 46 parameters lack schema descriptions. The description adds only minimal semantics for sorting, search, and include_avg_time_on_page, leaving the vast majority of parameters unexplained. This forces the agent to guess or rely on parameter names.

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 'Get page stats' with specific features (sorting, search, optional avg time). However, among sibling tools like pirsch_entry_pages and pirsch_exit_pages, it does not differentiate this general page stats tool from those specific ones, causing slight ambiguity.

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?

No guidance on when to use this tool versus alternatives such as pirsch_entry_pages, pirsch_overview, or pirsch_referrers. No mention of prerequisites, filtering logic, or expected use cases.

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