rig_create_preset

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

Annotations provide no readOnly/destructive hint, so the description carries the burden of disclosing effects. It only reveals that the preset is basic_chain (3 bones); it does not say whether this creates an armature, modifies the scene, requires a selected object, or returns a preset.

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 text is very short and has no filler, so it is concise. However, it is a fragment rather than a complete sentence and under-specifies the operation; brevity comes at the expense of basic orientation.

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 two-parameter creation tool with no output schema and sparse annotations, this description leaves too much implicit: what is created, what name does, and what the outcome is. The only concrete context is the 3-bone detail, which is not enough.

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%, so the description must document parameters. It partially clarifies that the preset value 'basic_chain' corresponds to a 3-bone chain, but it says nothing about the name parameter and gives no other accepted preset values.

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 is a bare parameter-value fragment ('preset: basic_chain (3 bones)') with no verb or object phrase, so it does not actually say what the tool does. The action 'create rig preset' only comes from the tool name and annotation title, which the description fails to restate or expand into a purpose.

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 about when to invoke this tool versus sibling tools like preset_apply, preset_create_from_scene, or rig_create_armature. There is no mention of prerequisites, applicable scenes, or when to choose an alternative.

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