sheets_create_pivot_table

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond that: it doesn't say whether the destination range is overwritten, whether a new sheet is created, or whether the operation fails on invalid column headers. With annotations present, the description should still contribute mutation-specific detail, and it contributes none.

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?

A single, front-loaded sentence with zero waste. It is efficient, though arguably undersized for a six-parameter tool with nested row/column/value structures.

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?

For a structurally complex tool (6 params, nested rows/values/columns objects) with no output schema, the description omits the mechanics an agent needs: that rows/columns define grouping, values define aggregation, and where the resulting pivot lands. Annotations cover safety only, leaving the functional explanation incomplete.

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 100%, so every parameter (spreadsheet_id, source_range, destination, rows, values, columns) is already documented in the schema, including A1 notation examples and aggregation enums. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 states a clear verb+resource ('Creates a pivot table in a Google Sheets spreadsheet'), so the agent knows exactly what operation is performed. However, it offers no differentiation from sibling creation tools such as sheets_create_chart or sheets_create_sheet, and does not hint at the required source range, row/column grouping, or value aggregation that make this tool distinct.

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?

There is no guidance on when to use this tool versus alternatives like sheets_create_chart or sheets_summarize_range, nor any stated prerequisites. The agent is left to infer usage entirely from the name and schema.

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