destinations_link

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

No annotations provided; description only flags write operation and required flags but omits behavioral details like idempotency, error cases, or effects of relinking.

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 a clear [WRITE] tag front-loaded; no unnecessary words.

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?

Covers requirements but lacks details on success behavior, error handling, or how to obtain destinationId; adequate for a simple mutation but could be richer.

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 covers 4 of 5 params; description adds example for destinationId and reinforces confirm flag, but leaves allowUserPermissionFeatureUpdate unexplained.

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?

Description specifies verb 'Link' and resource 'destination to GTM container', clarifying it's a write operation distinct from read siblings like destinations_get and destinations_list.

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?

Explicitly states prerequisites (GTM_MCP_ENABLE_WRITES=true and confirm=true), though it doesn't mention when not to use or alternatives for reading links.

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