rig.vertex_group_create

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

No annotations provided. Description only says 'Create' without disclosing behavioral traits such as whether it overwrites existing groups, required mesh mode, error handling, or side effects like modifying the mesh object.

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?

Extremely concise (one short phrase), but sacrifices necessary detail. While front-loaded, the description lacks critical information that would justify its 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?

Given no annotations, no output schema, and minimal description, the tool is underdocumented. An agent lacks information about side effects, success criteria, or required context (e.g., mesh object in scene).

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 description must add meaning. It adds nothing beyond the basic parameter names and types already in the schema. Does not clarify what 'mesh' expects (name, object, etc.) or constraints on 'name'.

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?

Clear verb 'Create' and resource 'mesh vertex group' specify the tool's function. Implicitly distinguishes from sibling 'rig.vertex_groups' which likely lists/reports groups. However, no explicit differentiation from other creation tools.

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 on when to use this tool versus alternatives like 'rig.vertex_groups' or other mesh creation tools. No prerequisites or context provided.

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