add_vertex_group

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which cover the mutation risk. However, the description adds no extra behavioral context, such as how existing vertex groups are affected, whether the operation is reversible, or if any object state is overwritten.

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 extremely short (one sentence), making it concise but also under-specified. It is front-loaded with the key action but omits useful detail. While it avoids unnecessary words, it does not earn its place by conveying additional value beyond the tool name.

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 simple tool with two parameters, explicit annotations, and an output schema, the description provides a baseline understanding. However, it does not mention potential caveats like needing an active mesh object or interactions with existing vertex groups. It is adequate but not comprehensive.

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%, and the description does not elaborate on object_name or group_name. It only mentions 'mesh', which hints at object_name, but does not explain default behavior for group_name or any constraints. The description fails to compensate for the low schema coverage.

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 'Buat vertex group pada mesh' clearly states the action (create) and the resource (vertex group on mesh), distinguishing it from sibling tools like remove_vertex_group and assign_vertex_weights. It uses a specific verb and noun, making the purpose unmistakable.

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, such as assign_vertex_weights or remove_vertex_group. There is no mention of prerequisites, selection requirements, or conditions under which this tool should be preferred.

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