gtm_transformation

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

With no annotations, the description must fully disclose behavior. It only mentions pagination for the 'list' action but omits important traits like whether actions are idempotent, what 'remove' does (destructive?), and the side effects of 'revert'. This is insufficient for a tool with multiple actions.

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 listing actions with a brief note on list pagination. It is efficient and front-loaded, but could be more informative given the tool's complexity. Still, it avoids unnecessary verbosity.

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?

Considering 9 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain what a transformation is, prerequisites, error scenarios, or return values for each action. The high parameter count and nested objects demand richer 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 100%, so baseline is 3. The description adds no parameter meaning beyond the schema; it only reiterates itemsPerPage behavior already documented. It does not enhance understanding of complex nested objects like createOrUpdateConfig.

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 states it performs 'all GTM transformation operations' and lists six actions, making the purpose clear. However, it could be more precise by specifying that it manages GTM transformation resources, distinguishing it from sibling tools which target other entities.

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 no guidance on when to use this tool versus alternatives or which action to choose for a task. Given multiple similar CRUD tools for other GTM entities, the lack of contextual advice reduces usability.

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