Move a drawing into an existing collection, or set its collection to null to leave it unorganized.
Move a drawing to an existing collection, or null for unorganized.
| Name | Required | Description | Default |
|---|---|---|---|
| drawingId | Yes | ||
| collectionId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states the move action and that null means unorganized, but does not disclose permissions required, whether the drawing must exist, or side effects. Mutation tool with no annotations; this is a gap but minimal disclosure.
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?
Single, front-loaded sentence with no waste. Appropriately sized for a simple move tool.
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?
Mutation tool with no annotations, 0% schema coverage, no output schema. Description is too sparse: missing prerequisites, error conditions, and parameter details beyond null handling.
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 description must compensate. It only clarifies that collectionId can be null for unorganized, which is already in the schema's anyOf. No description of drawingId or collectionId semantics beyond that.
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?
Clear verb+resource: moving a drawing to a collection. The 'or null for unorganized' adds behavior. However, does not distinguish from siblings like create_collection or list_collections, but the action is distinct enough.
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 explicit when-to-use vs alternatives. Implied that this is for moving existing drawings, but no exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.