List templates

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world). The description adds value beyond them with 'Refresh,' signalling that the call re-fetches/re-syncs template data rather than purely reading a cached snapshot, and it enumerates the payload fields (names, descriptions, tags, fonts, preview and thumbnail URLs) despite there being no output 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?

Two tight sentences with zero filler; the action and returned data are front-loaded and the environment note trails appropriately. Every clause earns its place by either naming the resource, the payload, or the valid context.

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?

Absent an output schema and with annotations covering read safety, the description supplies the essential missing piece by listing the fields returned. It is complete enough to invoke correctly, though it stops short of clarifying what distinguishes a 'template' from a 'site' in this ecosystem, which would fully close the gap.

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 zero parameters there are no argument semantics to document, so the baseline is 4. The description does not need to compensate for any schema gap, though it also adds nothing parameter-related (correctly, since there is nothing to add).

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?

States a specific verb (list) and resource (installed site templates) and even enumerates the returned fields, so the agent knows exactly what the call yields. However, it does not differentiate itself from the many sibling list tools (list_sites, list_pages, list_assets, list_blocks, list_skills, list_symbols), leaving the agent to infer what a 'template' is relative to a 'site'.

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 closing phrase 'Works from Home or Studio' gives a usable context clue for where the tool is valid, implying it is a discovery/listing action available outside the editor. It never states when to prefer this over the other list_* siblings or what prerequisites exist, so usage is only implied.

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