puppet_create_rig

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

No annotations are present, so the description carries full burden. It explains that parts are separate PNG images, layered, and independently animated. It also mentions returning a JSON summary. However, it does not disclose if the rig persists or any side effects.

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 front-loaded with a clear single sentence, followed by structured Args and Returns sections. It is well-organized but slightly lengthy due to the example; still 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?

Given the tool has an output schema (true), the description appropriately summarizes return behavior. All necessary input details are covered. The tool is single-purpose, and the description is complete.

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 0% with no parameter description in the input schema. The description compensates fully by providing a detailed example and explaining each field (name, image, position, scale, rotation, anchor, z_order) with semantics.

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 'Define a puppet character rig from body parts', specifying the verb 'Define' and resource 'puppet character rig'. It distinguishes from siblings like puppet_create_humanoid_rig by emphasizing custom body parts.

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 for custom rigs from parts, and alternatives like puppet_create_humanoid_rig or puppet_list_presets exist. However, no explicit when-to-use or when-not-to-use guidance is provided.

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