delete_sitemap

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

With no annotations, the description carries the burden of disclosing behavior. 'Delete (unsubmit)' communicates the mutating action and clarifies that it removes the sitemap submission rather than the hosted file, but it does not mention permissions, side effects on indexed pages, or error/response behavior. It is adequate but leaves gaps.

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 compact and front-loaded with the purpose, followed by a focused Args section. Every sentence adds necessary information and there is no filler.

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 delete operation with an output schema, the description provides all needed input context: where site_url comes from, how to format it, and exactly what sitemap_url should be. Nothing required for correct invocation is missing.

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 fully explain the parameters. It does: site_url is defined as an exact GSC property with examples and domain-property guidance, and sitemap_url is defined as the full sitemap URL to delete. This adds substantial meaning beyond the bare schema titles.

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 opens with 'Delete (unsubmit) a sitemap from Google Search Console,' which names the exact operation and resource. This clearly distinguishes it from sibling tools like submit_sitemap or delete_site.

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?

It does not explicitly name alternatives, but it gives concrete usage context: site_url must be an exact GSC property from list_properties, and it explains when to use a domain property versus a URL property. This is clear contextual guidance, though exclusions such as preferring manage_sitemaps for bulk operations are absent.

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