save_project

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

No annotations provided. Discloses that the tool performs a save (write operation) and distinguishes between save-in-place and save-as. Does not detail overwrite behavior or validation of path, but sufficient for a save 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?

Two sentences, front-loaded with the action, every sentence provides essential information with no waste.

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?

Given one parameter and no output schema, the description fully covers the tool's operation and parameter usage, with no obvious gaps.

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% but the description explains the parameter's purpose and format (ending in .stu), adding significant value beyond the schema's type-only definition.

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?

Clearly states it saves the open project and distinguishes between first save/save-copy (with path) and save-in-place (empty path). This differentiates it from siblings like export_project or new_project.

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?

Explicitly specifies when to provide a path (first save or save copy) and when to leave it empty (save in place). Could mention alternatives like export_project for other formats, but still clear.

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