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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: it names the required OAuth scope (project-write) and spells out that supplying projectId overwrites an existing owned project. It does not cover failure behavior, but it does more than restate the annotations.

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?

Three tight sentences with no filler, and the core action plus destination is front-loaded. The prerequisite scope sentence is slightly interleaved but still earns its place.

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 two-parameter mutation tool with no output schema, the definition covers the essentials: destination, required scope, and overwrite semantics. What is missing is the nature/format of the required 'model' payload and any indication of what success or failure returns, which keeps it out of the top tier.

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 coverage is 0%, so neither parameter is documented in the schema. The description compensates for projectId by explaining its create-vs-overwrite semantics, but 'model' is left entirely undefined — no format, type, or size expectations. Partial compensation puts this at the minimum-viable level.

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 states a specific verb and resource ('Save a model to ... VoxelDraft Cloud Projects') and names the destination scope, which separates it from local-model siblings like create_voxel_model or edit_voxel_model. It stops short of explicitly contrasting itself with any named alternative, so it lands just below the top tier.

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?

It gives a conditional usage rule for one path: 'Pass projectId to update and overwrite an existing owned cloud project.' That tells the agent how to choose between creating a new cloud project and overwriting one, but there is no guidance on when to use this tool versus edit_voxel_model or create_voxel_model.

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