folders_list

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

Discloses automatic pagination handling, which is a key behavioral trait. However, no information about performance, rate limits, or that it's a read-only operation. Without annotations, this is acceptable but not comprehensive.

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?

Two sentences, each providing essential information. Front-loaded with purpose, no redundant or extra words.

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 complexity (5 params, no output schema, no annotations), the description is minimal. It lacks details on output format, error handling, expected behavior when no folders exist, or how the pagination token works.

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 40% (2 of 5 parameters described). The description does not add meaning to the undocumented parameters (accountId, containerId, workspaceId), which are required but not explained.

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?

Description clearly states 'List all GTM folders in a workspace' with a specific verb and resource. It distinguishes from sibling tools like folders_get (single folder) and folders_entities (entities within a folder).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., folders_get for a single folder). Implied by 'all folders' but lacks when-not or prerequisite info.

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