set_vertex_position

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

No annotations are provided, and the description does not disclose behavioral traits such as error handling for invalid indices, whether changes are reversible, or if it modifies the original mesh. It only describes the basic action.

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 concise: one sentence for purpose and a bullet list of parameters. Every part serves a clear function with no redundancy or filler.

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 vertex move operation, the description covers the essential details. However, it lacks completeness regarding validation (e.g., invalid vertex_index), impact on mesh structure, and any prerequisites (e.g., object must be mesh).

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 description adds clear meaning for all 5 parameters (name, vertex_index, x, y, z) beyond what the schema provides, as the schema has 0% description coverage. It explains each parameter's role (e.g., 'Zero-based vertex index', 'Target world-space position').

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 it moves a single vertex of a mesh object to a world-space position, using a specific verb and resource. This distinguishes it from siblings like 'set_vertex_positions' which sets multiple vertices.

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 (e.g., set_vertex_positions or other transform tools). It only states what the tool does without context for selection.

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