get_sites

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

With no annotations, the description still communicates that this is a retrieval operation, returns a list of sites, and raises a BingWebmasterError on failure. It does not mention pagination or authentication, but this is a simple zero-parameter 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?

The description is short, front-loaded with the core action, and uses clearly labeled Returns and Raises sections. It is easy for an agent to parse quickly.

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?

The description covers the essential context: what the tool does, what it returns, and what error type may be raised. Since an output schema is present, the return structure does not need to be spelled out further, and no parameters require explanation.

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?

There are no parameters, so the parameter semantic burden is minimal. The phrase 'all sites' clarifies that the scope is account-wide, which is the only meaningful guidance needed.

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 uses a specific verb and resource: it retrieves all sites in the user's Bing Webmaster Tools account. This clearly distinguishes it from sibling tools that add, remove, or modify sites.

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 description makes the intended use obvious—call this when you need the full list of sites for the account. However, it does not explicitly compare against or contrast with similar sibling tools like get_site_roles or site mutation endpoints.

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