triggers_create

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

The description indicates a write operation via '[WRITE]' and mentions prerequisites, but fails to disclose what happens upon creation (e.g., returns the created trigger object, just a success response), potential side effects, or any destructive behavior. With no annotations, the description should provide more behavioral context.

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 short (one sentence plus a requirement note) and front-loaded with '[WRITE]'. While concise, it lacks substantive explanation; it could be more informative without becoming verbose.

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 write tool with 16 parameters, nested structures, and no output schema, the description is severely incomplete. It does not explain trigger concepts, how to construct the parameter objects, or typical usage patterns. Agents would struggle to invoke this tool correctly without additional context.

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 63%, meaning many parameters have descriptions in the schema itself. However, the tool description adds no additional explanation about parameters, their relationships, or usage patterns. For a complex tool with 16 parameters including nested objects, this is insufficient.

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 specific verb and resource. However, it does not differentiate this from other creation tools like tags_create or variables_create, leaving ambiguity about when to use this tool specifically.

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 required environment variables (GTM_MCP_ENABLE_WRITES=true, confirm=true) but provides no guidance on when to use this tool versus alternatives (e.g., triggers_update) or under what circumstances. No context on prerequisites or comparison with sibling tools.

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