Save project

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

With no annotations, the description carries the full burden. It discloses two behaviors: the default path behavior and the TurboWarp Desktop reload side effect. However, it does not mention whether the operation overwrites existing files, what happens if the project isn't open, or any error/return behavior. This is partial disclosure but not comprehensive.

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 with no fluff, front-loading the core action and then adding the default-path detail and a side effect. It is efficient and well-organized.

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 save operation with no output schema or annotations, the description covers the essentials but omits key details like return value, overwrite semantics, and behavior of the compressionLevel parameter. It is adequate for a straightforward call but not fully complete for an agent needing to handle edge cases.

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 description clarifies the 'path' parameter by repeating the default behavior, but the schema already covers that. The 'compressionLevel' parameter is undocumented in both schema and description, and the description adds no meaning for it. Given only 50% schema coverage, the description fails to compensate for the undocumented parameter.

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 action ('Write the open project back to an .sb3 file') with a specific verb and resource, and distinguishes it from siblings like open_project (load) and reload (reload). The default path detail adds precision. There is no ambiguity about what this tool does.

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 implies when to use it (when you want to persist the current project to disk) but does not explicitly state when not to use it or suggest alternatives. There is no mention of complementary tools like push_to_scratch or how saving differs from exporting. The guidance is implied rather than explicit, leaving some inference to the agent.

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