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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds the 50-item page cap and the cursor-following protocol, which are genuine behavioral details beyond annotations, but says nothing about ordering, result shape, or what happens when the account owns no sites.

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?

Two terse sentences, front-loaded with the core action and scope, with zero filler. The second sentence is telegraphic ('Follow next_cursor') and slightly fragmentary, but nothing 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?

For a two-parameter, zero-required list tool with no output schema, the description covers the page bound and paging mechanic but never characterizes the returned records or ordering, leaving an agent to infer the response shape from the schema's host description.

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 both parameters are already well documented (host semantics, including 'Does not create a site', and cursor provenance). The description's only added hint is 'Follow next_cursor', which largely restates the cursor schema description; 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 ('Read ... sites') plus a scope qualifier ('owned by the signed-in account') and an explicit page-size bound. It does not name the sibling get_site or otherwise disambiguate list-vs-single, so it falls short of a 5.

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?

The instruction 'Follow next_cursor' gives practical guidance on how to page through results, which implies continued use until exhausted. However, there is no explicit when-to-use-this vs get_site, and no stated exclusions or prerequisites.

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