gtm_create_trigger

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

No annotations are provided, and the description only states the mutation operation. It does not disclose that newly created triggers likely exist in the workspace draft until a version is created/published, whether trigger names must be unique, or what response is returned.

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 a single, front-loaded sentence with no filler. Every word contributes to stating the core operation and scope.

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 mutating tool with nested trigger configuration, multiple filter arrays, no annotations, and no output schema, a one-sentence description is under-specified. It omits creation lifecycle context, response shape, naming constraints, and filter semantics, making it harder for an agent to understand full behavior.

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?

The schema already documents accountId, containerId, and workspaceId, and provides structural detail for the trigger object. The description adds no parameter-level semantics, but the 75% schema coverage keeps this at baseline rather than below.

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 uses a specific verb 'Creates' with a clear object 'a new trigger' and scope 'GTM workspace'. This cleanly distinguishes the tool from siblings like gtm_list_triggers, gtm_get_trigger, gtm_update_trigger, and gtm_delete_trigger.

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 verb 'Creates' implies this tool is for new triggers, and sibling CRUD tool names clarify the surrounding alternatives. However, the description never explicitly states when to choose this over update/delete, nor does it mention prerequisites such as an existing workspace or container.

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