templates_import_from_gallery

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

Since no annotations are provided, the description carries the full burden. It discloses the write operation ([WRITE]), the required environment variable and confirm flag, idempotency ('importing one already present returns it unchanged'), and that the API supports it. It also warns about the tag type format, which is a nuanced behavior beyond simple schema.

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 long but every sentence contains essential information—prerequisites, behavior, downstream integration, common pairs. It's front-loaded with the primary purpose and uses [WRITE] to signal safety. However, the wall-of-text format could be better structured, so a 4 is appropriate.

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?

This tool is complex with 7 parameters and integration with tags_create. The description covers prerequisites, exact behavior, return value, and practical examples. With no output schema, it still clearly states 'Returns the installed template.' This is complete.

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 schema descriptions are generic (e.g., 'The GTM account ID'), but the description enriches them with concrete examples (github owner/repo pairs), explains the confirm flag requirement, and notes the sha default. This adds meaningful semantics beyond the raw 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?

The description clearly states the action: 'Install a Community Template Gallery template into a workspace by GitHub owner and repository.' This is a specific verb and resource, and distinguishes from sibling tools like templates_create by specifying the gallery import source.

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?

It explicitly says this is for using an official sandboxed template 'instead of Custom HTML,' and warns to 'never tell the user it is UI-only,' providing clear context for when to use it. It also provides downstream guidance on how to build tags with the returned template, reinforcing proper usage.

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