save_spreadsheet

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

With no annotations, the description carries the full burden and falls short: it says nothing about overwrite default behavior, whether the source sheet is modified, the attach/live-edit mode, or that this is a filesystem mutation. It repeats only the format-selection trait.

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, zero filler, with the core action and the format rule front-loaded. Every clause carries information an agent needs.

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 file-writing tool with no annotations and no output schema, the description covers format selection but leaves the write semantics (default overwrite behavior, source-preservation via copy, live attach) entirely to the schema. Adequate but with clear behavioral 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 coverage is already 83%, so the baseline is 3; the description earns above that by explaining the non-obvious rule that the extension drives the output format (.sta, .stw, .csv, .xlsx), which is not encoded in the schema and clarifies the 'out' parameter's meaning.

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 and resource ('Save a sheet to a new file') plus how the output format is chosen via file extension. It is clear on its own, but does not distinguish itself from the sibling export_csv, which plausibly overlaps for the .csv case.

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?

No guidance on when to use this versus export_csv or the other export-style siblings. The only directional hint is implicit in 'to a new file', and there are no stated prerequisites or exclusions.

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