create_armature

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

The description adds no behavioral detail beyond the annotation's destructiveHint=true. It does not explain what destructive action may occur or how this affects the scene, despite annotations indicating potential destructiveness. No contradiction, but also no elaboration.

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 a single concise sentence with no fluff. It is efficiently structured and front-loaded with the verb, though it sacrifices informative content for brevity.

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 creation tool with 3 parameters and no required ones, the description lacks critical context about object behavior, coordinate system interpretation, or potential conflicts with existing objects. The output schema may define return values, but scene effects and parameter semantics remain undocumented.

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%, so the description must compensate for parameter meanings. It only hints at add_root_bone via the parenthetical '(optional root bone)' and leaves name and location entirely unexplained, relying on schema defaults that are self-explanatory but lack context.

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 creates an armature object with a specific verb+resource combination. However, it lacks differentiation from sibling tools like create_object or add_bone, which may also create or modify objects.

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 guidance is given on when to use this tool versus alternatives such as create_object or rig_from_scratch. It does not mention prerequisites, contexts, or scenarios where this tool is preferred.

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