rig-vertex_group_create

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

No annotations are available, so the description must carry the full explanatory burden. It only restates the tool name-prefix 'create' and provides no extra behavioral context such as side effects, duplication behavior, validation, or required preconditions. The description adds no value beyond the tool's own name, so transparency is nearly absent (1/5).

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 short single sentence with no redundant words, but it is under-specified rather than concise. It contains only the bare restatement of the tool's purpose, offering no additional structure or front-loaded context that aids the agent. A score of 2 reflects under-specification while acknowledging the absence of verbosity.

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?

Even for a simple create operation, the description omits critical context: what happens if a vertex group with the same name already exists, whether the mesh must be a particular type, whether selections are used, or any error conditions. With no output schema and no extra description details, the tool leaves too much to infer. The description is incomplete for a tool that creates a data entity.

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 schema description coverage is 0%, and the description 'Create a mesh vertex group' does not elaborate on the parameters 'mesh' or 'name'. While the schema provides titles ('Mesh object to edit', 'Vertex group name'), the description contributes no additional semantic context and does not compensate for the lack of coverage. With 0% schema coverage and a non-explanatory description, a score of 1 is warranted.

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 'Create a mesh vertex group' uses a specific verb ('Create') and resource ('mesh vertex group'), making the primary action clear. It does not explicitly differentiate from sibling tools like rig-vertex_groups (list) or rig-assign_weights, but the intent is unambiguous. According to the rubric, this fits 'clear but no sibling differentiation' (4/5).

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 provided on when to use this tool versus alternatives, no prerequisites, and no use cases or exclusions. The description merely restates the tool's function without explaining when an agent should choose it over similar rigging tools. This is 'no guidance' (1/5).

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