sculpt_to_shape_key

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

No annotations are provided, so the description bears full responsibility. It mentions saving 'relative to the basis' and auto-creation of basis if missing, but does not disclose side effects like modification of existing shape keys or permanent mesh changes. Safety and prerequisites are not addressed.

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?

The description is short and front-loaded with purpose. Each sentence adds value, though the Args section partially duplicates schema content. Overall efficient.

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 tool with 3 params, no output schema, and no annotations, the description covers basic purpose and example usage but leaves gaps about exact behavior (e.g., how shape key is created, impact on mesh). Adequate but not thorough.

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?

The Args section adds minimal value: it lists parameter names and provides an example for shape_key_name. For basis_name, it notes auto-creation if missing. Schema coverage is 0%, so description partially compensates but lacks detailed constraints or format information.

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?

The description clearly states the tool saves the current mesh state as a shape key relative to the basis. It gives a concrete use case (face tracking workflow). However, it does not explicitly distinguish from sibling tools like 'ft_sculpt_shape_key' or 'cloth_to_shape_key', so it lacks full differentiation.

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 usage after sculpting a facial pose for face tracking. It does not provide when-not-to-use or alternatives. With many sibling tools, more explicit guidance would be beneficial.

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