origin_save_project

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

With no annotations provided, the description carries the full burden. It does not disclose whether the tool overwrites without confirmation, creates directories, or the behavior on existing files. The output schema exists but is not described, leaving behavioral traits unclear.

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 a single sentence of 10 words with no fluff. It is front-loaded with the verb 'Save' and immediately specifies the resource and target format.

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, no annotations, and an existing output schema, the description is partially complete. It lacks usage context (e.g., project must be open) and behavioral details (e.g., overwrite behavior). The output schema likely covers return values, but the description does not reference it.

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 a single 'path' parameter with no description. The description adds context that the path should be an OPJU/OPJ file path, which is helpful. However, it does not specify path format (absolute/relative) or any constraints, but given the simplicity, it adds sufficient value beyond the schema.

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 Origin project to a specific path, with the format OPJU/OPJ. It distinguishes from siblings like origin_open_project and origin_new_project by its save action.

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?

No guidance on when to use this tool vs alternatives; no prerequisites mentioned, such as the project needing to be open or path validation. The description does not contrast with export tools or other save-like siblings.

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