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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's closing 'Read-only' is redundant. It earns credit instead for disclosing non-obvious behavior: results are sorted by id descending, and built-in themes do not follow `createdAt` ordering, which affects pagination expectations.

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 opening sentence front-loads the core purpose and the sort behavior, and the trailing 'Read-only' is a cheap redundancy. The createdAt caveat is useful but slightly verbose, keeping it just short of ideal.

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?

With an output schema present and annotations covering the safety profile, the description only needs to add the sorting semantics and the downstream id usage — both of which it does. Nothing an agent needs to call the tool correctly 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 coverage is 100%, so limit, scope, and both cursor parameters are fully documented in the schema itself. The description adds only indirect color about id-based ordering, which loosely relates to the id-cursor pagination but does not extend the parameters' semantics. Baseline 3 is appropriate.

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 and resource (list themes) and defines the exact scope: the account's own themes plus built-in ones. An agent can immediately tell this apart from get_theme, list_theme_properties, and create_theme without opening a schema.

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?

Gives clear downstream context — use the returned id as `themeId` on a page or as `baseThemeId` to create a copy — which tells the agent why and how the result is consumed. However, it never names an alternative tool or a when-not condition (e.g., when to prefer get_theme for a single theme).

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