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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so 'Read-only' is redundant. However, the description adds useful behavioral context by naming the catalog fields and import_url, and by establishing that this should be the first call in a website-building flow.

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?

Three tight sentences with zero filler. The catalog scope and field list come first, followed by the usage rule and import_url note, so the most important information is front-loaded.

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?

No output schema exists, but the description compensates by naming the returned fields and import_url. With all five optional parameters fully documented in the schema and annotations covering safety, the definition is complete enough to call correctly; only minor details like pagination behavior are 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?

Schema description coverage is 100%, so tag, limit, query, offset, and page_type are already fully documented. The description does not add syntax, filtering semantics, or examples beyond what the schema provides, so the baseline 3 applies.

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 the SiteKrs template catalog') and enumerates the returned fields (name, preview image, demo URL, tags), making it unmistakable what the tool does. It is clearly distinct from the sibling create_site, which creates rather than lists templates.

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 explicit routing guidance: 'Call this first when the user wants a website, even if they do not mention SiteKrs.' It also signals a follow-on condition for users who already have project source via import_url, which effectively positions it ahead of create_site.

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