sn_aggregate

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

No annotations provided, so description carries the burden. States it returns stats without fetching records (read-only implication), but does not disclose required permissions, rate limits, or other behavioral traits like whether grouping affects the result structure.

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?

Single sentence that efficiently conveys the tool's purpose and key feature (no record fetching). No wasted words.

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 description is minimal but covers the core functionality for a simple aggregate tool. Lacks details on output format, error handling, or complex use cases, but given the absence of an output schema, extra context on return structure would be helpful.

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 coverage is 60% (descriptions for field, aggregate, group_by). Description adds no extra meaning beyond summarizing aggregate types; it does not explain the 'query' or 'table' parameters beyond the schema. Baseline 3 is appropriate as schema already provides partial descriptions.

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?

Clearly states the verb 'Run' and resource 'aggregate on any table' with specific operations COUNT/SUM/AVG/MIN/MAX and optional group_by. Distinguishes from sibling tools like sn_query by specifying statistical aggregation without fetching 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?

Implies usage for statistics without fetching records, but lacks explicit when-to-use versus alternatives (e.g., sn_query for records). No exclusions or prerequisites mentioned.

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