app-file_save_copy

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

With no annotations, the description reveals useful behavioral information: it creates a copy and leaves the active file path unchanged. Still, it does not clarify overwrite behavior, error handling, or the return value, leaving some important trait undisclosed.

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 concise sentence that states the action and key side effect without padding. It is front-loaded and every word contributes value.

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 one-parameter tool, the description covers the core operation and its distinguishing side effect. The main missing detail is overwrite/conflict behavior, but given the tool's low complexity, the description is largely complete.

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 property is titled 'Absolute output .blend path', which already explains the parameter's purpose. The description adds no further mapping details, and with 0% schema description coverage, it provides minimal compensation, but the single path parameter is largely self-explanatory.

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 uses a specific verb ('save a copy') and resource ('current file'), and immediately distinguishes itself from related tools with 'without changing the active file path'. This clearly sets it apart from app-file_save_as, making the purpose unambiguous.

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 phrase 'without changing the active file path' provides clear contextual guidance for when to use this tool over sibling save operations. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a full guideline.

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