save_script

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

Annotations already declare readOnlyHint=false with destructiveHint=false, so the agent knows this mutates state but is not framed as destructive. The description usefully clarifies that the no-path case rewrites the live script and the path case writes elsewhere, but it is silent on whether an existing file at `path` is overwritten or what happens on failure — the key risk for a save operation.

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 sentence with the primary action front-loaded and the conditional branch attached immediately after. No filler, no redundancy, and the quoted "save as" label makes the mode switch instantly scannable.

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?

An output schema exists, so return values need no explanation, and with only one optional parameter the surface area is small. Still, for a state-mutating tool the description omits overwrite/error semantics that an agent needs to call it safely, leaving the definition adequate but not complete.

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% (the `path` property carries only a title and null default), so the description must compensate. It does explain the semantic trigger for `path` (save-as mode) and that it should be a .nk path, but adds no guidance on absolute vs relative paths, extension handling, directory creation, or overwrite behavior.

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?

Names a specific verb (save) and resource (the live script), and explicitly splits the behavior into save-in-place versus save-as depending on `path`. It does not reference any sibling tool (e.g., open_script) to further triangulate scope, but the verb+resource combination is unambiguous.

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 definition gives a usable selection rule between its own two modes: omit `path` to save in place, supply `path` for "save as". It stops short of stating prerequisites or when an agent should prefer this over related workflow tools such as open_script, so usage is implied rather than fully guided.

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