Gtm.List Variables

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

With no annotations and a minimal description, the agent receives zero information regarding rate limits, performance, or specific data constraints, which is critical for an operational list tool.

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 definition is a single, highly focused sentence that contains zero waste. It is immediately understandable and placed before any structured data.

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?

While it is technically complete enough to invoke correctly (single required parameter), it lacks necessary context for an agent to use it efficiently, such as defining naming conventions or potential limitations of the list.

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?

Since there is only one required parameter and the input schema lacks parameter descriptions, the description succeeds in defining the necessary input: the 'workspace path.' This compensates for the 0% schema description coverage.

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 identifies the action (List) and the resource (user-defined variables), making it unambiguous what the tool does for the agent.

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 definition fails to provide guidance on when to use this tool relative to other similar GTM list tools, offering no alternatives or specific use-case context beyond basic function.

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