webflow_list_sites

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is fully covered. The description adds the scoping detail that results are limited to the authenticated account's sites, which is genuinely useful context, but says nothing about result size, pagination, or ordering.

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?

A single short sentence with no filler and the resource front-loaded. It is perhaps over-terse rather than bloated, but nothing in it is wasted.

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 description should say roughly what comes back (site id, name, etc.) since downstream tools need those IDs. Annotations cover safety and the single param is fully documented, but the return-value picture is left entirely implicit.

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?

Only one parameter exists and schema description coverage is 100% ('Webflow API token'), so the schema already documents everything. The description adds no syntax, auth-flow, or scope detail for the token beyond the phrase 'for the account'. Baseline 3 applies when the schema carries the parameter semantics.

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 Webflow sites') plus a scope qualifier ('for the account'), so the agent knows this is a discovery/enumeration call over sites. It does not, however, distinguish itself from the sibling webflow_get_site (single-site) or webflow_list_collections/items, which the agent must differentiate by name alone.

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?

There is no explicit when-to-use guidance, no mention of when to prefer this over webflow_get_site, and no stated preconditions beyond the implicit need for an access token. The agent must infer that this is the entry point for discovering site IDs used by other Webflow tools.

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