rsap_save_project

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It mentions overwriting the current file in the omit case, but does not clarify whether a supplied path will overwrite an existing file, what happens if no project is open, or whether a success/failure response is returned.

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 compact and front-loaded: two introductory sentences immediately convey the save modes, followed by a concise Args definition. Every sentence provides useful information without 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?

Given the single parameter and no output schema, the description covers the core usage well. The main gaps are minor: no explicit mention of preconditions (e.g., an open project) or edge-case behavior for Save As overwriting an existing file. Still, it is nearly complete for this simple tool.

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 has 0% description coverage, but the Args block fully compensates by explaining that path must be an absolute .rtd path (Save As) or None to overwrite the current file. This adds important meaning beyond the schema's raw anyOf string/null and default.

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 'Save the current model' and distinguishes two modes: Save As (with path) and Save in place (without path). This is a specific verb+resource that is distinct from sibling project tools like new/open/close.

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?

Provides explicit conditional usage: pass an absolute .rtd path for Save As, or omit it to overwrite the currently open file. There is no alternative save tool among the siblings, so the guidance is clear and actionable even without explicit alternatives.

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