templates_update

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 mentions prerequisites but does not explain whether updates are full replacement or partial, irreversible consequences, error handling, or authorization beyond the environment variable.

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?

Two sentences with no wasted words. Critical information is front-loaded: operation, resource, prerequisites, and input format.

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?

With 7 parameters (5 explicit), no output schema, and no annotations, the description covers the key points but omits details like fingerprint usage, return value, or error scenarios. Adequate but not thorough.

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%, baseline 3. The description adds value by specifying that bodyJson must contain the full resource as a JSON string, which goes beyond the schema description. This clarifies the update semantics.

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 starts with '[WRITE] Update an existing GTM template,' clearly stating the verb and resource. It distinguishes from sibling templates_create, templates_get, templates_delete, templates_revert, and templates_list by focusing on update.

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 clear context: it is a write operation requiring GTM_MCP_ENABLE_WRITES=true and confirm=true. It does not explicitly state when not to use it or list alternatives, but the write and confirm flags give sufficient guidance.

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