set_morph_target

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

Beyond annotations (destructiveHint=true), description adds critical context: changes are runtime-only and lost on reload. Also requires user consent, which is a key behavioral trait. No contradictions with annotations.

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?

Description is somewhat repetitive, stating the runtime-only preview and the requirement to ask user twice. Could be more concise without losing meaning, but still front-loaded with key information.

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?

Given no output schema, description omits return value but covers the essential behavior (temporary, user must decide). It references runtime preview but doesn't mention prerequisites like mesh having morph targets. Still sufficient with sibling tools available.

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 is 100% with descriptions for all 5 parameters, so description need not elaborate much. However, it does not add extra meaning beyond the schema, just reiterates the runtime nature. Baseline 3 is appropriate.

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?

Clearly states 'Set morph target influence on a mesh', specifying the action and target. Distinguishes from sibling tools like morph_targets which likely only read targets, by emphasizing runtime-only preview and user confirmation for persistence.

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?

Explicitly instructs the agent to ask the user first whether they want runtime preview or persistent code change, providing clear and necessary guidance for correct usage. This prevents unwanted side effects and aligns with the tool's temporary nature.

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