Delete sitemap

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description doesn't repeat those. The description confirms the destructive nature with 'Remove/delete'. It adds the behavior that site_url format errors can cause permission errors even for legitimate owners, which is useful context. No contradiction with annotations.

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 main description is a single concise sentence, but the site_url guidance in the schema is lengthy and highly informative. The description text itself is appropriately short, though it could have front-loaded a warning about the destructive nature.

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 destructive operation with clear annotations (destructiveHint=true), the safety profile is conveyed. The site_url format explanation covers the main usage pitfall. An output schema exists so return value documentation isn't needed. The description could mention idempotence implications, but idempotentHint already covers that.

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%, so parameter semantics are already well-documented in the schema. The description additionally clarifies the site_url format pitfall and instructs calling sites.list first, which adds real value beyond the schema. The feedpath parameter is documented with an example in the schema itself.

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 clearly states the specific action ('Remove/delete a submitted sitemap') and the resource ('sitemap from your Google Search Console account'). It differentiates from siblings like sitemaps.list and sitemaps.submit by focusing on the delete operation, though it doesn't explicitly name alternatives.

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 context implies deletion of an already-submitted sitemap. The site_url parameter description gives important guidance about property formats and calls out that sites.list should be called first if unsure. However, it doesn't explicitly state when not to use this tool or contrast it with sitemaps.submit or sitemaps.get.

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