Get Insights

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. It mentions 'aggregated' but does not explain aggregation behavior, default time windows, filtering semantics, or any side effects. It also doesn't clarify whether results are ordered, paginated, or limited beyond what parameters imply.

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 concise sentence that is easy to parse and front-loads the primary function. However, it may be too sparse, omitting important context a longer, still concise description could include.

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 6 parameters, no output schema, and no annotations, the description is insufficient. It doesn't explain the return structure, typical use cases, or how it differs from the many sibling analytics tools. The lack of behavioral and usage detail makes the tool harder to select or invoke correctly.

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 schema has 100% description coverage, with each parameter (metric, group_by, days, limit, etc.) having its own description. The tool description restates the core relationship between metric and group_by but adds no new meaning beyond the schema. Baseline 3 is appropriate because schema handles the heavy lifting.

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's action: 'Get aggregated insights for a metric grouped by a dimension.' It uses a specific verb and identifies the resource/operation. However, it does not explicitly distinguish itself from sibling tools like 'query' or 'get_dashboard', which could also produce aggregated insights.

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 is provided about when to use this tool versus alternatives such as 'get_retention', 'get_funnel', or 'query'. The description only states what it does, not when it should be chosen or excluded.

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