delete_sitemap

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

No annotations are provided, so the description bears the full burden. It identifies the action as deletion (mutation) and explains parameter details, but does not disclose side effects (e.g., reversibility, impact on indexing) or required permissions.

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 concise, using a structured 'Args' block with clear parameter descriptions. Every sentence serves a purpose, and there is no redundant information.

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 tool with an output schema (though not shown), the description covers both parameters adequately and provides necessary context for usage. It does not explain the response, but the output schema can fill that gap.

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 0%, but the description significantly adds meaning by explaining site_url with examples (including domain vs subdomain) and specifying sitemap_url as the full URL. This goes 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?

The description explicitly states 'Delete (unsubmit) a sitemap from Google Search Console.' The verb 'delete' and resource 'sitemap' are clearly defined, distinguishing it from siblings like submit_sitemap or 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?

Provides clear guidance on the format of site_url (exact GSC property URL with examples) and explains domain property usage. It does not explicitly state when to avoid using this tool, but the purpose is distinct enough that alternatives are obvious.

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