gtm_list_accounts

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

No annotations are provided, so the description must carry the full behavioral burden. It adds one useful constraint—only accounts accessible to the authenticated user—but says nothing about pagination behavior, response shape, or whether 'all' means auto-paginated, leaving the pageSize/pageToken behavior unclear.

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 with no filler. The core action, resource, and auth scope are all front-loaded and immediately usable.

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?

With no output schema and no annotations, the description is too sparse to fully prepare an agent. It does not describe the return fields, pagination continuation, or the fact that returned account IDs feed into downstream GTM tools like gtm_list_containers.

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%, and the description does not mention pageSize or pageToken, let alone explain that they control result size and paging. The phrase 'Lists all' even risks implying that no pagination parameters are needed.

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 uses a specific verb ('Lists') and names the exact resource ('Google Tag Manager accounts accessible to the authenticated user'). This clearly distinguishes it from sibling tools like ga4_list_accounts and gbp_list_accounts, which list accounts from different Google products.

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 implies this is the GTM account-discovery entry point, and that it should be used before account-scoped tools like gtm_list_containers. However, it does not explicitly mention when to use it versus ga4_list_accounts or state any exclusions.

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