gtm_get_tag

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 does not state that this is a read-only operation, does not mention authentication requirements, error handling, or return value expectations. For a get operation, the read-only nature is somewhat evident, but the lack of any behavioral disclosure is a significant gap.

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 concise sentence, with no wasted words. However, it is too sparse to be fully helpful. It is not overlong, but it omits essential context, so it earns a mid-range score rather than a higher one.

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 4 required parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain the need for account/container/workspace IDs, what the function returns, or any potential errors. This is inadequate for an agent to invoke the tool correctly.

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 0%. The description mentions 'by id,' which provides minimal insight into the 'tag_id' parameter, but the other three required parameters (account_id, container_id, workspace_id) are completely unexplained. The description does not compensate for the lack of parameter information in the schema.

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 action: 'Get a single tag by id.' It specifies the verb (Get), the resource (tag), and the scope (single vs. multiple), which distinguishes it from sibling tools like gtm_list_tags. However, it does not provide any additional context about the required IDs or the hierarchical structure.

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 offers no guidance on when to use this tool versus alternatives like gtm_list_tags. There is no mention of when not to use it, no prerequisites, and no reference to other tools. The usage context is only implied by the phrase 'single tag by id,' which is insufficient.

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