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

Annotations already cover idempotency, mutability and open-world scope, so the bar is lower. The description still adds real context the structured fields lack: the write-access prerequisite on the site and the graceful-failure behavior when changes are disabled.

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?

Two tight sentences: action and effect first, prerequisite and failure mode second. No filler, everything front-loaded.

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 two-parameter mutation with annotations covering safety and no output schema, the description supplies the missing pieces: authorization requirement and failure semantics. Slightly short on how submission relates to sibling submit/list tools.

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 description coverage is 100%, with both siteUrl and sitemapUrl well documented including fallback formats, so the schema carries the burden and baseline 3 applies. The description adds no parameter-level detail beyond what the schema provides.

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 specific verb (add/resubmit) plus resource (sitemap) plus platform (Bing Webmaster Tools), and the effect ('so Bing reads it'). It is immediately distinguishable from sibling bing_list_sitemaps.

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?

Explains the benefit and covers the resubmit case explicitly, but does not route the agent between this and nearby alternatives such as bing_submit_urls, nor state a when-not-to-use condition. Clear context, no exclusions.

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