gtag_config_delete

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

With no annotations, the description takes full burden. It explicitly states the destructive nature (delete) and the requirement for confirmation, signaling the need for caution. However, it does not discuss irreversibility or side effects, but the confirmation mechanism adds a layer of safety.

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 extremely concise, front-loading the HTTP method and action. Every word adds value; no redundant information. It fits in a single sentence without sacrificing clarity.

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?

The description covers the core action and prerequisites but lacks information about post-delete behavior, such as return values or error states. Since there is no output schema, additional context would help the agent understand what to expect after a successful deletion.

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%, with each parameter described in the input schema. The description adds no additional detail about parameters; it only restates the confirmation requirement already in the schema. Baseline score of 3 is appropriate.

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 the verb 'delete' and the resource 'GTM gtag config', making the purpose unambiguous. The '[DELETE]' prefix reinforces the action, and the tool name is self-explanatory, distinguishing it from sibling tools that operate on other entities like tags or triggers.

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 prerequisites 'GTM_MCP_ENABLE_DELETES=true and confirm=true', which is necessary but does not provide guidance on when to use this tool versus alternative delete tools for other GTM resources. No context on when not to use or comparison to siblings is given.

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