create_vertex_group

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

No annotations are present, so the description carries the burden of disclosing behavior. It only states the core create/assign action but omits details like idempotency, behavior if the vertex group already exists, error handling for invalid objects, or how vertices are interpreted (e.g., zero-based indices). This is a significant gap for a mutation tool.

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, front-loaded sentence that states the core action and optional behavior with zero wasted words. It is maximally concise while still conveying essential meaning.

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?

While an output schema exists, the operation involves 4 parameters and no annotation safety context. The description covers optional params but lacks guidance on required params (object, name) and lacks behavioral caveats. It is minimally adequate for a simple create operation but leaves ambiguities that could cause incorrect invocation.

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?

With 0% schema description coverage, the description must clarify parameters. It explains 'vertices' and 'weight' explicitly ('optionally assigning vertices with a weight'), but leaves 'object' and 'name' unaddressed beyond their literal names. This partially compensates but not fully.

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 action ('Create a vertex group') and the optional assignment of vertices with a weight. This distinctly differentiates it from sibling tools like get_vertex_groups (viewing groups) and assign_vertex_weights (modifying existing groups).

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?

The description implies the use case (creating a group) but does not explicitly contrast with alternatives like assign_vertex_weights for modifying existing groups. No when-not or prerequisite context is provided, though the name and verb make the primary use clear.

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