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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description earns modest credit for disclosing that results include status information, but says nothing about pagination, result ordering, empty-list behavior, or what happens if the site is not verified in Bing.

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 fragment with zero filler, and the key scope (Bing sitemaps) is front-loaded. It reads as a noun phrase rather than an action statement, which costs a little immediacy but no space 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 single-parameter read-only listing tool with full schema documentation and no output schema, the description covers what is returned and for which provider. Only minor gaps remain: no note on response shape (since no output schema exists) or on whether unknown sites return an error versus an empty list.

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 coverage is 100% and the single siteUrl parameter is well documented, including the requirement to use the exact format returned by bing_list_sites. The description adds no parameter meaning beyond 'for a site', so the baseline of 3 applies.

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 names the concrete resource (sitemaps and feeds) and the provider scope (submitted to Bing), and 'with their status' clarifies what is returned. It is a noun phrase rather than a verb, but 'list' in the name plus the resource description makes the operation unambiguous. It does not explicitly contrast with gsc_list_sitemaps or yandex_list_sitemaps, relying on the 'Bing' qualifier to differentiate.

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?

Usage is implied: an agent would call this to inspect which sitemaps Bing has for a given site. There is no explicit when-to-use statement, no mention of the read-only, non-mutating counterpart bing_submit_sitemap, and no prerequisite guidance such as needing a site URL obtained from bing_list_sites (that hint lives only in the schema).

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