save_level

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the basic save behavior and the all_dirty option, but does not reveal important traits such as whether saving overwrites existing files, what 'dirty' means, or what happens if no level is open. This is a significant gap for a mutation tool.

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 and 15 words, front-loaded with the primary action. Every phrase adds value, including the conditional all_dirty behavior, with no redundancy or filler.

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 simple tool with one optional parameter and no output schema, the description covers the core behavior and the parameter's effect. It could benefit from clarifying 'dirty' and prerequisites (e.g., requires an open level), but overall it is sufficiently complete for its simplicity.

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 schema provides only the type and default for all_dirty, with no semantic description. The tool description compensates by explaining the effect of setting all_dirty to True, which clearly defines the parameter's meaning in context.

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 clearly states the tool saves the current level, with a specific verb 'Save' and resource 'level'. It also differentiates the all_dirty variant, which distinguishes it from the sibling tools that focus on actors and content assets.

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 description provides clear context for when to use this tool (to save a level) and explicitly specifies the conditional behavior for all_dirty=True. It does not enumerate exclusions or alternatives, but the context is unambiguous among the sibling tools.

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