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

The description goes well beyond the annotations by describing what is returned: which theme is live, versions, whether a theme builds, and how many changes are held back by a validator error, pending build or open update merge. That return-shape detail is valuable since there is no output schema. It does not address the internally odd annotation set (readOnlyHint=true alongside destructiveHint=true and idempotentHint=false), so an agent gets no help reconciling whether this call is safe or mutating — the description itself does not contradict them.

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 content is economical — three short units, no filler — and the 'call this first' directive is placed at the end where it is easy to catch. However, the opening is a sentence fragment that delays the actual statement of purpose, so the structure is not front-loaded as well as it could be.

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 one-parameter read listing with no output schema, the description supplies the important missing piece: an enumeration of the fields an agent will receive and what the 'held back changes' count means. The workflow instruction about picking a theme before mutating rounds it out. Minor gaps remain around ordering and behaviour on a site with no themes, but nothing an agent needs to call it correctly is absent.

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?

There is a single parameter and schema coverage is 100%, with the schema already explaining that 'site' is named as list_sites names it. The description adds only the scoping notion that the whole listing applies to one site of the account. With the schema doing the heavy lifting, this is the baseline 3.

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 makes clear that this returns every theme on a single site — installed or bundled — with the live theme marked, versions, build status and pending-change counts. That is enough to separate it from neighbours such as list_theme_files, get_theme_settings, theme_history and search_theme. It loses a point because it opens with a fragment ('On one site of the account, named in site.') rather than a verb+resource statement of what the tool does.

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 gives explicit workflow guidance: 'Call this first' and, if the site has multiple themes and the person did not name one, ask which before changing anything. That is a concrete when-to-use rule with a follow-up action. It stops short of naming the alternatives it displaces (e.g. search_theme, get_theme_settings) or stating when not to call it, so it is not a full 5.

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