refresh_pivottables

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

No annotations are provided, so the description must carry the behavioral burden. It says what is refreshed, but it does not disclose permissions, side effects, whether dependent formulas recalculate, behavior when no PivotTables exist, or what the tool returns.

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?

Two short sentences, front-loaded with the action and followed by the trigger condition. There is no wasted wording.

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 simple one-parameter refresh tool with no output schema, the description is adequate: it identifies the operation and the condition for using it. Minor gaps remain around side effects and failure/no-op cases, but the core information needed to invoke it is present.

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?

The single workbookId parameter is already fully documented in the schema, including its optionality when only one workbook is connected. The description adds only the general phrase 'in the workbook' and does not add further parameter semantics, so the schema does the heavy lifting.

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 gives a specific verb and resource: refresh all PivotTables in a workbook. It clearly scopes the operation to PivotTables, but it does not distinguish it from the related sibling calculate_workbook, which could also be relevant after data changes.

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 states a clear usage condition: use after data changes when pivot summaries must be current. It does not name exclusions or an alternative tool such as calculate_workbook for non-pivot recalculation, so guidance is helpful but not exhaustive.

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