Set Workbook Properties

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

The description adds substantial behavior beyond the annotations: no-parameter calls are read-only, manual calc mode causes stale caches, an auto-backup and atomic verified save occur, and the operation refuses while the file is open in Excel. It also discloses the conditional read-only nature despite the destructiveHint, clarifying rather than contradicting the annotations.

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 compact and front-loaded: the first sentence establishes the primary purpose and parameter groups, while the remaining sentences add critical behavioral caveats. Every sentence earns its place, and there is no filler or repetition of schema/default information.

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 the core behavior, conditional read-only semantics, backup/save guarantees, and an important refusal condition, which is strong for a complex tool. Yet it still omits semantics for several parameters (allow_loss, verify_com, path) and does not describe the result/return shape, which matters because there is no output schema. An agent could call it correctly in most cases but may mis-handle the undocumented options.

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?

With schema description coverage at 0%, the description carries the burden and does so well for most parameters: it names the document property fields, explains calc_mode values, and describes iterative_calc with max_iterations and max_change. However, allow_loss, verify_com, and path receive no semantic explanation, leaving meaningful gaps for a 15-parameter tool.

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?

States a specific verb ('set') and a precise resource ('core document properties ... and calc settings'), enumerating the affected fields. The scope is clearly workbook-level metadata/calculation behavior, which distinguishes it from sibling tools like set_cell, manage_worksheet, or get_workbook_metadata. The added nuance about read-only reporting with no parameters further sharpens the purpose.

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 context for use is implied: use this to change document properties or calculation settings, or to report current values when no parameters are given. It also gives a hard prerequisite ('Refuses while open in Excel'). However, it does not explicitly mention when to prefer an alternative sibling such as get_workbook_metadata or audit_formulas, and there are no when-not-to-use directives.

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