containers_combine

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

With no annotations provided, the description attempts to disclose behavioral traits by marking it as [WRITE] and warning with a hazard symbol, but it does not explain the full impact (e.g., whether the source container is deleted or remains) or required permissions beyond the environment variable.

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 consists of two clear, front-loaded sentences that convey the action, requirements, and a warning without unnecessary detail.

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 complexity of a merge operation and no output schema, the description lacks details on post-merge behavior (e.g., what happens to the source container, how conflicting settings are resolved) and does not fully compensate for missing annotations.

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 description adds little value beyond what the schema already provides. It mentions key parameters like containerIdToCombine and confirm but does not elaborate on settingSource or allowUserPermissionFeatureUpdate.

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 ('combine/merge'), the resource ('another container into this one'), and specifies the source and target by ID, distinguishing it from sibling tools like containers_create or containers_move_tag_id.

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 indicates prerequisites (requires GTM_MCP_ENABLE_WRITES=true and confirm=true) and provides a clear context for when to use the tool, but does not explicitly state when not to use it or suggest alternatives.

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