save_level

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Save' clearly conveys a persistent write operation, but the description does not mention overwrite semantics, failure behavior if no level is open, or other side effects. It is not misleading, just minimally transparent.

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?

One sentence with no filler; the verb is front-loaded and every word adds meaning. The description is appropriately sized for a no-argument save operation.

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 tool with no parameters and an output schema, the description is the minimum viable: it identifies the action and the object. However, it leaves unstated whether the operation overwrites an existing save or how errors are surfaced, and there are no annotations to cover these details.

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 tool takes zero parameters, so the schema fully covers parameter semantics. A baseline of 4 is appropriate because there is nothing for the description to add.

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 names the specific action (save), the resource (level), and the state condition (currently open). This cleanly distinguishes it from sibling tools like save_prefab and load_level without requiring the agent to inspect schemas.

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 phrase 'currently open' implies the tool is for persisting the active level, but the description gives no explicit guidance about when to use it versus alternatives or what preconditions must hold. Usage is inferred rather than clearly stated.

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