List Tag Manager workspaces

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

The read-only and non-destructive nature is already indicated by annotations. The description adds context about the number of workspaces but does not disclose additional side effects or limitations. Since annotations cover the main safety aspects, the description meets the baseline.

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 concise, two sentences, and starts with the primary purpose. It adds relevant contextual information without extraneous details.

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 mentions that workspace IDs are part of the output, which is useful. It also explains the typical single-workspace scenario. While it doesn't describe the full output schema or error handling, for a simple list tool this is acceptable given the existence of an output schema (though not shown). It could be improved by explicitly stating the return format, but it's fairly complete.

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?

The schema provides only parameter names and types with no descriptions. The description does not elaborate on the parameters, such as how to obtain account/container IDs or any constraints. This leaves the agent to infer from the tool name and context.

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 (List) and the resource (workspaces under a GTM container). It also explains the typical use case with the Default Workspace, which helps distinguish from other list tools.

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?

It explicitly mentions that workspace IDs are needed for get_gtm_workspace_diff, providing a concrete usage scenario. The note about parallel drafts also guides expectations. However, it doesn't explicitly contrast with other list tools, but that's not critical.

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