render_save_preset

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

Annotations already set destructiveHint: true and readOnlyHint: false, indicating a write operation. The description adds the useful behavior that a missing extension is automatically completed to .rps, which is beyond the annotations. However, it does not disclose whether existing files are overwritten, or any error conditions, leaving some behavioral gaps.

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 extremely concise, consisting of two sentences (one in Chinese and its English equivalent). The core purpose is front-loaded, and the extension behavior is included without redundancy. There is no wasted wording, and the bilingual format serves clarity without adding bulk.

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 simple imperative tool with one parameter and no output schema, the description covers the essential action and file extension behavior. It does not state whether existing files are overwritten, but given the destructiveHint annotation, the agent can reasonably infer a write operation. The description is sufficiently complete for an agent to call the tool correctly.

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 coverage for the 'path' parameter is 100%, so the baseline is 3. The description adds semantic value by specifying that a missing extension is automatically appended, which is critical for correctly forming the file path. This goes beyond the schema's generic description of the path.

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 verb 'save' and the resource 'current render preset' to a .rps file. It is unambiguous and easily understood. However, it does not explicitly differentiate from the sibling tool 'render_load_preset' by naming it, relying on the inherent contrast between save and load.

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 usage: to save the current render preset as a .rps file. It provides no explicit guidance on when to use this tool versus alternatives like render_load_preset or export_engine_preset, and no conditions or exclusions are mentioned. The intended use is inferable from the straightforward action, but no alternatives are called out.

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