List custom templates

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

Annotations already declare the read-only, idempotent, non-destructive safety profile. The description adds useful behavioral context beyond annotations: template code is not returned, and omitting workspace_id triggers a cached lookup of the Default Workspace. It does not cover error or permission behavior, but the added return-content and caching details are valuable.

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 dense but efficient: it front-loads the template scope, then immediately documents the container and workspace parameters. Every sentence adds necessary information, with no filler.

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 two parameters, 0% schema description coverage, and an available output schema, the description supplies all caller-relevant details: resource scope, return limitation, container formats, workspace default behavior, and caching. Nothing essential for correct invocation is missing.

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%, so the description carries the full burden and does so well. It defines container formats (GTM-XXXXXXX, linked G-/AW- destination id, or API path accounts/<a>/containers/<c>) and explains that workspace_id is numeric and can be omitted to use the cached Default Workspace.

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-like action (listing custom/community-gallery templates) and the exact resource scope: templates installed in the workspace. It also clearly distinguishes the returned data by noting that template code is not included, so an agent can tell this apart from sibling list/get tools.

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?

Usage is implied by the resource and container/workspace context, and the default-workspace behavior is explained. However, the description does not explicitly state when to use this tool versus alternatives such as other list tools, nor does it provide when-not-to-use guidance.

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