uae_source_aggregate

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

With no annotations, the description explains the basic behavior (grouping and reducing) but does not disclose whether it is read-only, any rate limits, or error conditions.

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 short (two sentences plus a code example) and front-loaded, efficiently conveying the core functionality without extra 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?

Despite having an output schema, the tool has 8 parameters and aggregation logic, yet the description only covers group_by and vague aggregation types, leaving significant gaps for proper use.

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 0%, and the description only explains the group_by parameter format. The other 7 parameters (top, limit, query, metric, dataset, source_id, value_field) are left completely unexplained.

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 groups records and applies aggregation functions (count, sum, avg, min, max). It also distinguishes itself as a generalized form of uae_market_snapshot, providing sibling differentiation.

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?

It mentions being a generalized form of uae_market_snapshot, which gives context on when to use it, but does not explicitly state when not to use it or provide alternatives.

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