triggers_create

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

No annotations are provided, so the description must disclose behavioral traits. It only indicates a mutation via '[WRITE]' and the requirements. Missing details: success returns, error states, idempotency, or that it creates a new trigger entity. The description does not contradict annotations (none exist), but it is insufficient for a mutation 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 a single sentence with a clear '[WRITE]' prefix, making it front-loaded and efficient. However, it is too brief for a complex tool, sacrificing completeness for brevity.

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 tool has 19 parameters, nested objects, and numerous sibling tools, the description lacks high-level context such as what a GTM trigger is, its relationship to other entities, or guidance on parameter groups. The schema partially compensates, but the description is insufficient for an agent to correctly structure complex triggers.

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 68%, so the schema itself documents most parameters. The tool description adds no parameter-level information beyond the requirements. Baseline score of 3 is appropriate as the description provides minimal extra value.

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 it creates a GTM trigger with a '[WRITE]' prefix. The verb and resource are specific. Although it doesn't elaborate on what a trigger is, it distinguishes from sibling tools like triggers_delete and triggers_update by stating 'Create'.

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 provides explicit requirements (GTM_MCP_ENABLE_WRITES=true and confirm=true), which helps the agent know when invocation is valid. However, it does not mention when to use this tool over alternatives like triggers_update or triggers_list, nor does it explain prerequisites beyond the required fields.

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