voxelforge_save

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

The description lacks detail on side effects (e.g., overwriting existing files), behavior when scene_name is empty, or required permissions. With no annotations, the description fails to disclose important behavioral traits.

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) with no wasted words. However, it is under-specified for a tool with parameters and output schema, sacrificing informativeness for 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?

The description does not cover return values (output schema exists but ignored), does not differentiate from export or create scene tools, and omits behavior on default parameter. Incomplete given the tool's role.

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 has 0% description coverage, and the tool description does not explain the scene_name parameter (e.g., its role, default behavior if omitted). No added semantic value over the bare schema.

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 (save) and the target resource (scene to ~/.voxel-forge/scenes/). It differentiates from siblings like voxelforge_create_scene (create new) and voxelforge_export_* (export to other formats).

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 such as voxelforge_export_vox or voxelforge_load. The description does not mention prerequisites or context for usage.

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