insert_subtotals

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly notes that the tool is destructive, modifies the sheet structure, and inserts new rows, and it describes the return format. This covers key concerns, though it does not mention error handling or side effects beyond structural changes.

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 well-structured with a one-sentence purpose followed by clear Args, Returns, and Notes sections. It is concise, avoids redundancy, and every line of the description adds value.

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 covers all parameters, notes destructiveness, and describes the return value, providing a solid basis for invocation. However, some details remain unspecified, such as the exact format for group_col/value_col and the full list of subtotal_func codes, leaving minor gaps.

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 0%, making the description's parameter explanations essential. It provides concise but meaningful definitions for all six parameters, including the default for subtotal_func and the purpose of include_grand_total, adding significant value beyond the schema.

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 inserts SUBTOTAL formula rows after each group in a sorted sheet, providing a specific verb, resource, and scope. This distinguishes it from sibling aggregation tools that may not modify the sheet structure.

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 indicates the need for a sorted sheet as a precondition, but does not provide explicit guidance on when to use this tool versus alternatives like aggregate_data or column_statistics. No exclusions or alternative recommendations are given, leaving usage to inference.

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