set_properties

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

With no annotations, the description carries the full behavioral burden, and it only discloses the deferred-persistence workflow via save_all. It says nothing about whether properties merge or replace existing ones, what happens on an invalid path, whether unknown keys are rejected, or whether the change is reversible before save.

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?

Two sentences, zero filler, with the primary action front-loaded and the follow-up requirement placed second. Nothing is padded or redundant.

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?

There is no output schema and no annotations, while the schema contains an unconstrained nested properties object, so the description would need to explain expected keys and result behavior. It covers only persistence, leaving the most ambiguous part of the tool undocumented.

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 description coverage is 0% across both parameters, and 'properties' is an open-ended nested object with additionalProperties true whose accepted keys and value types are entirely undocumented. The description adds no parameter meaning beyond repeating the field name in prose, leaving the agent unable to construct a correct call.

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 and resource ('Set properties on an asset') scoped to the active mod, which is clearer than a bare name restatement. It does not distinguish itself from siblings like duplicate_asset or clone_row, and leaves 'properties' undefined, so an agent knows roughly what it does but not the scope of what can be set.

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 instruction 'Call save_all afterwards' implies this is a staging mutation that requires an explicit persist step, which is genuinely useful context. However, there is no guidance on when to use this versus other mutation tools, no prerequisites (e.g., asset must exist, mod must be open), and no exclusions.

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