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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own — nothing about pagination, whether nested folders are returned, ordering, or whether folders are scoped per-container/per-workspace path.

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 operative sentence is short and front-loaded, which is good, but the trailing "Tools revision: d80f65c0." is build metadata that consumes space without helping an agent select or invoke the tool.

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?

An output schema exists, so return values need not be described, and annotations cover safety. For a one-parameter list tool this is nearly sufficient, but the undocumented workspace argument and the absence of any hierarchical/pagination context leave a real gap.

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 single required parameter `workspace` has 0% schema description coverage, so the schema gives no format hints. The description only echoes "in a workspace" without saying whether this is a numeric ID, a resource path, or a name, and gives no example — it does not compensate for the coverage gap.

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 a specific verb and resource ("List folders") scoped to a workspace, which is enough to distinguish it from write operations like gtm_create_folder and gtm_update_folder. It does not, however, differentiate it from the cluster of other list tools (gtm_list_tags, gtm_list_variables, gtm_list_workspaces) beyond the resource noun.

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?

There is no when-to-use guidance, no prerequisite (e.g. needing a workspace or container ID first), and no mention of alternatives or follow-up tools such as gtm_update_folder. The agent must infer context entirely from the title and siblings.

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