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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value by enumerating the returned fields (id, name, subdomain, locale, status draft/published, public URL) and positioning the tool as the prerequisite for obtaining a siteId. It stops short of describing pagination or how limit affects results.

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: what it returns, when to call it, what comes back. The usage trigger is front-loaded right after the purpose, and no sentence is redundant.

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 no output schema, the field enumeration in the description is exactly what an agent needs to know what it will receive. The remaining gap is differentiation from list_pages/get_site and any hint about result volume, which matters for a list operation.

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 single `limit` parameter is fully documented in the schema (100% coverage), so the baseline of 3 applies. The description adds nothing about default page size or whether results are truncated, which is the one place it could have supplemented the 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 names a specific verb and resource ('List all landing pages ... owned by the user on Convika'), which is clearer than the bare name list_sites. However, it never addresses the obvious ambiguity with the sibling tools list_pages and get_site — the 'sites vs pages' terminology overlap is left for the agent to resolve.

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 concrete activation contexts: 'When the user asks about their existing pages, wants to edit or check a page, or you need a siteId for any operation, call this tool first.' That is a strong positive trigger, but there is no exclusion clause telling the agent when to prefer list_pages or get_site instead.

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