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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not carrying the safety burden alone. It still adds real value by disclosing that the tool reads back the result ('verified = steht danach nicht mehr in bing_list_sitemaps') and that URLs stay in the index, which is exactly the non-obvious side effect an agent needs.

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?

Three short sentences with the action and verification behavior front-loaded and the parameter note last. Little waste, though the parenthetical aside breaks the flow slightly.

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 output schema exists, so return values need no explanation, and the description covers side effects and the optional workspace. It omits what happens on failure (sitemap not found) and whether the sitemap must already exist, which matters for a destructive tool with required params.

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 0%, so the description must carry parameter meaning. It documents the workspace parameter well (slug, optional when only one workspace exists) but says nothing about sitemap_url's expected format, beyond the self-explanatory name and the fact that it identifies the sitemap to remove.

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 gives a specific verb and resource (remove sitemap from Bing Webmaster Tools) and explicitly names the sibling bing_list_sitemaps as the way to verify removal. An agent can distinguish this from bing_submit_sitemap and bing_list_sitemaps without opening either schema.

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?

'Die Seiten bleiben im Index' implies this is purely a sitemap-registration removal, not a deindexing action, which helps set expectations. However, it never states when an agent should choose this over bing_submit_sitemap or what precondition must hold (the sitemap must already be submitted). Usage is implied rather than spelled out.

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