Move drawing

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description usefully clarifies that omitting the folder target relocates to the top of the Space and that a move is confined to one Space. It says nothing about what happens to the drawing's previous placement, required permissions, or why the call is non-idempotent.

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?

Two short sentences with zero filler; the destination behaviour leads and the Space restriction follows as the qualifying constraint.

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 move tool with full schema coverage, no output schema, and annotations covering the mutation profile, the description supplies what is needed to call it correctly. Only permission requirements and the effect on the source location remain unstated.

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 100%, so the baseline would be 3, but the description adds meaning beyond the schema: folderId must resolve to a folder inside the drawing's own Space, a constraint the schema does not state. The 'leave it out' destination semantics are duplicated from the schema rather than extended.

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?

States a specific verb (moves) and resource (drawing) plus both destination modes (into a folder, or to the top of its Space). The distinction from siblings like create_drawing, trash_drawing, and restore_drawing is immediately obvious.

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?

Gives a concrete precondition: the target folder must belong to the drawing's Space, and cross-Space moves are impossible. It does not name alternatives or say when to prefer this over e.g. create/trash, but the operating context is clear.

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