save_unreal_target

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

Annotations already declare non-readonly, destructive, idempotent, closed-world behavior. The description adds a useful side-effect boundary by saying it does not open a project or import assets, but it does not explain what the destructive save may overwrite or what permissions are needed.

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?

A single front-loaded sentence with the negative scope immediately following. Every phrase adds information and there is no wasted text.

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?

An output schema exists and annotations cover safety and idempotency, so return-value detail is not required. However, for a destructive save with five required nested fields at 0% coverage, the description should better explain the target contract.

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?

There is only one top-level parameter, but it is a nested UnrealTarget object with five required fields and 0% schema description coverage. The description refers only to 'explicit Unreal target fields' and does not clarify project_file, skeleton_path, skeletal_mesh_path, destination_path, or asset_name.

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?

States a specific verb, resource, and scope: save Unreal target fields for this workspace, and rules out opening projects or importing assets. Sibling differentiation is implicit rather than explicit, since it does not name get_unreal_target or the handoff tools.

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 workspace scoping implies a setup/persistence context, and the 'does not open a project or import assets' clause gives one exclusion. It does not name alternatives for reading the target or executing a handoff, so use-versus-alternative selection is left to inference.

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