aggregate-rum

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds behavioral context by detailing the types of statistical computations and grouping operations performed, without contradicting the annotations. It does not describe potential side effects or advanced behaviors like result limits or pagination.

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 sentence that is clear and free of unnecessary words. It effectively conveys the core functionality without 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 absence of an output schema, the description does not explain the return format (e.g., a list of grouped results or a single aggregate). It also omits details like pagination or time range limitations, making it adequate but not fully complete for complex use cases.

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 100%, so the baseline is 3. The tool description mentions 'count, avg, percentiles' and 'grouping by fields', which map to the 'aggregation' enum and 'groupBy' parameter, but it does not add significant new semantic meaning beyond what the parameter descriptions provide.

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 'aggregate', the resource 'RUM data', and the type of operations (statistical computations like count, avg, percentiles, and grouping by fields). This effectively distinguishes it from siblings such as 'search-rum-events' (raw event retrieval) and 'create-rum-metric' (metric creation).

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 does not explicitly specify when to use this tool versus alternatives, nor does it provide when-not-to-use guidance. While it implicitly suggests aggregation of RUM data, it lacks direct references to sibling tools or exclusion criteria.

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