gtm_create_tag

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

No annotations are provided, so the description must carry the behavioral burden. It adds a safety note about operating only on sandbox, but does not disclose return format, side effects, required permissions, or idempotency. More detail is needed for a creation 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 extremely concise—two sentences that front-load the core purpose and an important safety note. No superfluous information.

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 creation tool with no output schema and no annotations, the description is incomplete. It does not explain what happens after creation (e.g., immediate activation, need to create a version), nor does it provide context relative to sibling tools like gtm_preview or gtm_create_version.

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 baseline is 3. The description repeats 'Full GTM tag JSON' without adding new constraints or format details. It adds no extra meaning beyond the schema's description.

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 'Create a new tag in the sandbox workspace,' specifying the action (create) and resource (tag) with scope (sandbox). This distinguishes it from siblings like gtm_update_tag, gtm_get_tag, and gtm_list_tags.

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 mentions 'only operates on sandbox workspace,' providing a constraint. However, it lacks guidance on when to use this tool versus alternatives like gtm_update_tag or gtm_create_variable, and does not specify prerequisites or context.

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