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

Annotations already declare a non-destructive, non-idempotent, closed-world write, so the marginal bar is low, and the description does add substantive context they do not: the folder is staged and never published to the live container. It omits what happens on a name collision and where exactly the staged folder lives, which keeps it from a 5.

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 core constraint is front-loaded in a single dense sentence with no preamble. The trailing 'Tools revision: 5c9bea8f.' line is metadata noise that does not help an agent decide or invoke.

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?

An output schema exists, so return values need not be explained, and the staging behavior is covered. However, with 0% parameter documentation and no usage guidance for a mutation tool, an agent still lacks what it needs to supply 'container' 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%, so both parameters depend entirely on the description, which says nothing about them. In particular 'container' is ambiguous — an ID, a public container ID, or a name — and the agent gets no help from either source.

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 and resource ('Create a folder') plus its scope ('STAGED in the managed AdCopilot workspace, never published'), which distinguishes it from gtm_update_folder and gtm_list_folders by effect. It stops short of explicitly naming a sibling or explaining the staged-vs-live relationship, so it is clear but not fully differentiating.

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?

There is no when-to-use guidance: nothing says when to create a folder rather than update an existing one, or that gtm_list_folders should be checked first to avoid duplicates. The only implied guidance is the staging constraint.

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