folders_move_entities

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

No annotations are provided, so the description bears full responsibility. It indicates it's a write operation requiring confirmation, but it does not disclose side effects (e.g., whether moves are reversible, impact on other folders) or any other behavioral traits. This is insufficient for a write tool.

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 very concise (two short sentences) and front-loaded with the key action. Every word provides value, but the structure could be improved by separating the requirement details.

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?

Given the tool has 8 parameters, no output schema, and is a write operation, the description lacks completeness. It does not explain the return value, any constraints, or post-move behavior. Sibling tool folders_entities exists but is not referenced for context.

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 description coverage is 50%, meaning half of the parameters already have descriptions in the schema. The description adds semantic value by linking 'tags/triggers/variables' to the tagId, triggerId, and variableId parameters. However, it does not elaborate on accountId, containerId, workspaceId, or folderId beyond their names, partially compensating for the schema gaps.

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: 'Move tags/triggers/variables into a folder.' It specifies the resource (folders) and the operation (moving entities), distinguishing it from sibling tools like folders_create, folders_delete, folders_entities, folders_get, folders_list, and folders_update.

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?

The description includes explicit prerequisites: 'Requires GTM_MCP_ENABLE_WRITES=true and confirm=true.' It also marks the operation as write with the '[WRITE]' prefix. However, it does not discuss when to avoid using this tool or alternatives beyond the implicit differentiation from siblings.

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