raw_save

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It openly states that the action 'may open a dialog or change project state,' which is valuable context for a mutation-like operation. However, it does not specify what dialog, what state changes, or whether the action overwrites the existing file; the vague phrasing leaves significant room for interpretation.

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 short and front-loaded, stating the primary purpose first. The 'Save:' prefix is somewhat redundant with 'Save the current project,' but the overall length is appropriate and every sentence contributes practical information.

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 zero-parameter, no-output-schema tool, the description covers the essential points: what it does, that it takes no arguments, and that it may have side effects. The advice to 'inspect the command name first' hints at ambiguity but is not fully explained. Overall, it is adequate for an agent to use the tool safely in most 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 input schema has zero properties and the description explicitly says this is a 'no-argument' action. With no parameters to document and full schema coverage, the description adds appropriate confirmation that no arguments are needed. This meets the baseline for zero-parameter tools plus explicit reinforcement.

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 states a clear verb and resource: 'Save the current project.' This is specific enough to understand the tool's core function. However, it does not differentiate it from sibling tools like project_save or raw_save_as, and the opening 'Save:' is redundant with the name.

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 the tool: to save the current project. It also provides a caution to 'inspect the command name first,' which is a weak usage guardrail. It does not explicitly contrast with alternatives such as raw_save_as or raw_save_copy, so an agent must infer the appropriate selection context.

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