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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restatement and the description correctly avoids repeating it. What it does add is tenant scoping ("the user's" sites) and returned fields, though it says nothing about pagination, result caps, or whether sites in other orgs/cloud accounts are included.

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?

One short sentence, front-loaded with the verb and resource, with the payload described at the end. Every clause carries information and there is no filler.

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 input parameters, a full output schema, and annotations covering the safety profile, there is little left for the description to carry, and the scoping phrase addresses the main ambiguity. The only residual gap is how results are bounded across orgs or cloud accounts, which the open-world annotation hints at but the description never resolves.

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 there is no parameter semantics to explain; the baseline for a no-arg tool applies. Nothing in the description misleads about inputs.

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 user's deployed static sites") and adds the returned attributes (status and URL), so the agent knows exactly what it gets. It does not, however, distinguish itself from nearby siblings such as list_site_deployments, list_site_releases, or list_organizations, which an agent must infer from names 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?

The use case is implied strongly by the phrasing — call it to get a catalog of the user's sites — but there is no explicit when-to-use, when-not-to-use, or named alternative. No preconditions or ordering relative to siblings like get_site_details or list_organizations is given.

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