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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses a non-obvious side effect: the first write to a container creates a draft 'AdCopilot' workspace if none exists. It also explains the safety model — no Tag Manager publish permission, so nothing reaches the site until a human publishes — which is exactly the kind of context annotations cannot convey.

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 staging constraint is front-loaded in the first sentence and the two paragraphs earn their place. The trailing 'Tools revision: d80f65c0.' is internal metadata that adds nothing to tool selection.

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 mutation tool the description does well on behavior and safety, and an output schema exists so return values need not be explained. However, with zero schema description coverage, the complete absence of parameter guidance (especially how to identify a container) leaves a real gap in calling the tool correctly.

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 0% for two required parameters ('container' and 'name'), so the description carries the full burden and fails to explain what a container identifier looks like (ID vs. path vs. account/container pair) or any constraints on the folder name. Neither parameter is mentioned anywhere in the description text.

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 names a specific verb and resource ('Create a folder') and pins down the scope with 'STAGED in the managed AdCopilot workspace (never published)'. That scope qualifier also separates it from sibling write tools such as gtm_create_tag or gtm_update_folder without the agent needing to open another schema.

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?

Usage is implied by the staging explanation and the note that a draft 'AdCopilot' workspace is auto-created on the first write, but there is no explicit when-to-use/when-not-to-use guidance and no pointer to siblings like gtm_list_folders or gtm_update_folder. The agent can infer context but must do the routing work itself.

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