aggregate_records

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

With no annotations, description carries full burden. It explains aggregation behavior, available aggregators, default actions (e.g., omit measures to count records), and a cap on limit. Does not explicitly state read-only nature, but server-side aggregation implies no mutation.

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?

Description is front-loaded with purpose, followed by a clear list of parameters. Every sentence is informative, no fluff or repetition. Efficient and well-structured.

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?

Covers all input parameters including optional ones, provides examples, and mentions system limits (ODOO_MAX_RECORDS). Output schema exists, so return format is not needed in description. Complete for a complex tool with 7 parameters.

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%, so description fully explains all 7 parameters. Provides syntax examples (e.g., 'date_order:month'), allowed aggregators, defaults, and usage notes. This compensates for missing schema descriptions and adds significant value.

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 'Group and aggregate records server-side', which is a specific verb-resource combination. Distinguishes itself from raw data retrieval tools like read_records or search_read by emphasizing server-side aggregation.

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?

Provides context for use ('one call instead of pulling rows') and detailed parameter explanations, but lacks explicit 'when not to use' or direct comparison to sibling tools. However, the description is sufficient for an informed choice.

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