pirsch_overview

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

With no annotations, the description carries the full burden. It discloses that data is 'cached', which is a key behavioral trait for an agent to understand potential staleness. However, it omits other details like data freshness windows or rate limits.

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?

Two short, front-loaded sentences. The first conveys purpose, the second adds an important constraint. Every word serves a purpose with no redundancy.

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 low complexity (one parameter, no output schema), the description covers basic behavior. However, it fails to explain what 'overview statistics' includes, which is critical given the many sibling tools with more specific metrics.

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 description provides no details about the only parameter, domain_id, even though the schema has 0% description coverage. The agent must rely entirely on the parameter name for meaning.

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 tool retrieves 'overview statistics for a domain', using specific verb and resource. However, it does not explicitly distinguish from siblings like pirsch_total or pirsch_visitors, leaving the agent to infer that 'overview' is a composite summary.

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 notes that 'filters do not apply', implying this endpoint is for unfiltered overviews. It offers no explicit guidance on when to use this tool over alternatives, nor does it list alternative tools for filtered queries.

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