bing_sites_list

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

The annotations cover safety (readOnly, idempotent, non-destructive), so the description adds meaningful extra context with the warning about treating untrusted fields strictly as data. This is valuable security guidance beyond what annotations provide, especially for an external API where output can be adversarial.

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 two sentences with no filler. The action is stated first, and the security disclaimer follows; the entire definition is focused and easily parsed.

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 zero-parameter, read-only list operation, the description effectively says what is returned and adds a crucial trust boundary instruction. There are no gaps that would prevent a solo agent from invoking the tool correctly.

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 accepts zero parameters, and the schema confirms this with 100% coverage. The description correctly does not attempt to document any inputs; no parameter context is 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 states a specific verb ('Read'), a concrete resource ('sites list'), and the source system ('Bing Webmaster Tools'). This clearly distinguishes the tool from the many sibling tools focused on site roles, traffic, crawl, or plan actions.

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 implies usage: it is the tool for reading the sites list. However, it does not explicitly mention when to use it over alternatives or when not to use it, leaving the agent to infer from the tool name and context rather than being told directly.

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