triggers_create

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

With no annotations provided, the description carries full burden but only states it is a write operation and lists prerequisites. It lacks details on side effects, return values, or error behaviors, which are critical for a write 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 very concise, only one sentence with a prefix. It is front-loaded with the '[WRITE]' indicator. However, it may be too brief, sacrificing necessary 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 (11 parameters, nested objects, no output schema), the description is severely incomplete. It does not explain the return value, impact, or relationship to sibling tools.

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 only 45%, and the description adds no additional meaning to any parameter. It does not explain parameters like filter, eventName, or parentFolderId beyond their schema descriptions.

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 GTM trigger' with a '[WRITE]' prefix, specifying the verb and resource. It distinguishes from sibling tools like triggers_delete or triggers_update. However, it does not elaborate on what a GTM trigger is or its context.

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 the requirement of GTM_MCP_ENABLE_WRITES=true and confirm=true, providing explicit conditions for use. However, it does not compare to alternatives or indicate when not to use this tool.

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