wave_set_ai_preset

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

With no annotations provided, the description carries the full behavioral burden and discloses important traits: it mutates a specific file, uses a confirmation-then-execute pattern, and requires an approval flag. It does not mention permission requirements, overwrite semantics for existing presets, or special handling for the api_token parameter beyond the schema's note.

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 two sentences, front-loaded with the action and file path, and immediately follows with the critical safety workflow. Every sentence earns its place with no wasted words.

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 essential confirmation workflow and file destination for a mutation tool, which is important given the lack of annotations and output schema. However, for an 11-parameter write tool that handles an api_token, it omits details about overwrite behavior, permission requirements, and the shape of the first-call confirmation.

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 the schema already documents all 11 parameters thoroughly. The description only adds meaning for the approved parameter by explaining its role in the confirmation workflow, which is marginal beyond the schema.

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 specific verb (create/update), resource (Wave Terminal AI model preset), and destination file (~/.waveterm/aipresets.json). It clearly distinguishes this write operation from the sibling read tool wave_get_ai_presets.

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 two-step confirmation workflow is explicitly described, including the requirement to pass approved=true to execute. However, there is no guidance on when to use this tool versus alternatives such as wave_get_ai_presets, nor are there explicit exclusions or prerequisites.

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