templates_list

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

The description adds the behavioral trait of automatic pagination, which is valuable since no annotations exist. However, it does not disclose other traits like permissions, rate limits, or that the operation is read-only, leaving some gaps.

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 with no wasted words. The first sentence immediately conveys purpose, and the second adds key behavior. Very concise and front-loaded.

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?

For a list tool without output schema, the description covers the essential functionality and pagination behavior. It could mention that results include template objects, but that is implied. Overall adequate for the complexity level.

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 100% schema coverage, the parameters are already well-described. The description reinforces that pagination is handled automatically (relating to maxPages and pageToken) but adds no new semantic detail beyond the schema.

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 it lists all GTM templates in a workspace, using specific verb 'list' and resource 'GTM templates', distinguishing it from sibling tools like templates_get or templates_create. The scope 'in a workspace' is explicit.

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, though the mention of automatic pagination implies it's for full listing. Without exclusion or sibling differentiation, the agent must infer usage context from the name and purpose.

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