ft_combine_shape_keys

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

No annotations provided. Description does not disclose behavioral traits such as destructiveness (e.g., whether source shape keys are modified), permissions, or effects on existing shape keys.

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 plus argument list with no fluff. Every sentence adds value, efficiently conveying core functionality.

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?

No output schema. Adequately describes inputs and purpose but lacks details on behavior when output_name already exists, or return value.

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%. Description adds meaning for 'sources' parameter (JSON array with name and weight), but 'mesh_name' and 'output_name' lack additional explanation beyond the schema.

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?

Description clearly states 'Combine multiple shape keys with weights into a new shape key,' using specific verb+resource. This distinguishes it from sibling tools like ft_mirror_shape_key or ft_sculpt_shape_key.

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?

No explicit when-to-use or when-not-to guidance. Implied usage is for combining shape keys, but no mention of prerequisites, exclusions, or alternatives like ft_create_arkit_shapes.

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