set_morph_target_deltas

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the agent knows this is an idempotent mutation that can destroy data. The description adds the delta payload format and the return shape (valuable since no output schema exists), but does not state that existing deltas are overwritten or what permissions are required.

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 with the core operation front-loaded and the return shape placed second. Efficient with no filler, though it is slightly compact given the nested payload complexity.

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 four-parameter mutation tool with no output schema, the description compensates by documenting the return contract and the delta payload structure. Annotations cover the safety profile, so the remaining gap (destructive-replacement semantics) is minor.

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 100%, so all four parameters are already documented. The description restates the delta dict keys (vertex_index, position_delta, normal_delta) that the schema example already shows, adding no meaning beyond the structured data. Baseline 3 applies.

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 vertex deltas for a morph target on a specific LOD'), which an agent can clearly separate from siblings like get_morph_target_deltas or set_morph_target_generated_by_engine. The scope (morph target, specific LOD) is precise.

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 when to use it (writing vertex deltas for a morph target), but gives no explicit when-to-use guidance, prerequisites, or named alternatives. No exclusions or conditions are stated.

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