list_gtm_workspaces

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description does not need to reiterate safety. It adds context about workspace usage but no additional behavioral traits like auth or rate limits. This is adequate given the annotations.

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 brief (4 sentences) and front-loaded with the main action. It is efficient, though the parameter context could be integrated without adding much length.

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 presence of an output schema and read-only nature, the description covers purpose and usage well. However, the missing parameter explanations leave a gap in completeness, especially for a tool with two parameters.

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?

With schema description coverage at 0%, the description must compensate. It mentions 'under a GTM container' implying gtm_container_id is needed, but it does not explain gtm_account_id or the parameters' format or purpose. This is insufficient for effective tool use.

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 'list', the resource 'workspaces (drafts)', and the context 'under a GTM container'. It differentiates from siblings like get_gtm_workspace_diff and get_gtm_tag by focusing on listing workspaces.

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 explicitly says 'Workspace IDs are needed for get_gtm_workspace_diff', indicating a prerequisite use case. It also explains the typical workspace cardinality (single default vs. multiple drafts), which guides when to use this tool.

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