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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context by clarifying that results are scoped to the authenticated tenant and that the tenant is remote, but says nothing about pagination, ordering, or result size limits for a list operation.

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 front-loaded sentence with the scope qualifier attached directly to the verb and resource. No filler, no redundancy with the title.

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 parameterless read of a well-scoped resource with no output schema, the description covers the essentials: what is listed and whose sites they are. Minor gaps remain around result shape and whether an empty tenant yields an empty list, but nothing an agent needs to call it 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?

The tool takes zero parameters, so the schema baseline of 4 applies and the description cannot add parameter meaning that doesn't exist. Acceptable but not exceptional.

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 (List) and resource (sites) with an explicit scope: sites belonging to the authenticated tenant. This differentiates it from list_pages, list_collections, and other list_* siblings by resource. It does not, however, contrast itself with nearby tools like select_site or create_site.

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?

No zero-parameter call is inherently discoverable, so implied usage is the ceiling here. The description gives no explicit when-to-use, when-not-to-use, or pointer to the related select_site sibling, leaving the agent to infer that this is the entry-point enumeration of tenants' sites.

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