sn_aggregate

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

No annotations are present, and the description provides no behavioral details beyond the basic operation. It does not mention that the tool is read-only, what permissions are required, rate limits, or the structure of the returned aggregate results.

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, front-loaded with the action, and contains no redundant words. It efficiently conveys the tool's core functionality.

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?

With 6 parameters and no output schema, the description is minimal. It explains the core purpose but omits details about return format, error behavior, or constraints, which are important for a query tool with grouping and display_value options.

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 descriptions cover all 6 parameters (100% coverage), so the baseline is 3. The description adds only 'optional grouping' which maps to group_by but does not enrich parameter meaning beyond schema definitions.

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 runs aggregate queries (COUNT, AVG, MIN, MAX, SUM) on a ServiceNow table with optional grouping, distinctly differentiating it from sibling tools like sn_query or sn_get that retrieve raw records.

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?

Usage is implied via the aggregation verbs and table context, but no explicit guidance is given about when to choose this tool over alternatives like sn_query for raw data, or any exclusions for unsupported aggregate types or table restrictions.

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