delete_sitemap

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does add 'write' and 'supports dryRun,' which signal mutation and a preview capability beyond the tool name. However, it omits whether deletion is irreversible or whether special permissions are required, leaving only partial transparency.

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 a single efficient sentence that front-loads the core purpose and immediately surfaces the dryRun capability. There is no filler or redundant repetition of the schema.

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 simple 3-parameter delete operation with full schema coverage and an output schema present, the description covers the essential purpose and dryRun behavior. It lacks an explicit irreversibility caveat, but the 'write' label partially compensates for the missing annotations, making the description adequate for correct invocation.

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 the schema already documents siteUrl, feedpath, and dryRun with meaningful details. The description only repeats dryRun's existence without adding new semantic value, so the baseline of 3 is appropriate.

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 states a specific verb ('Remove'), a clear resource ('submitted sitemap'), and a target ('Search Console property'), which distinguishes it from related siblings like submit_sitemap and list_sitemaps. The parenthetical 'write' also clarifies the mutation type immediately.

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?

There is no guidance on when to use this tool versus list_sitemaps or submit_sitemap. It does not mention that a user should first list sitemaps to obtain the feedpath, nor does it warn about destructive effects beyond the terse 'write' label. The dryRun option is mentioned but not framed as a recommended workflow.

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