Delete sitemap

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

With no annotations present, the description carries full responsibility for disclosing side effects; it states the delete action and OAuth requirement but does not say whether removal is permanent, what happens to the property, or whether the sitemap URL must still exist. This is a minimal disclosure for a destructive operation.

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 two short sentences with no filler; the action is front-loaded and the OAuth requirement is a meaningful addition. Every sentence earns its place.

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?

This is a simple two-parameter tool, but with no output schema, no annotations, and zero parameter documentation, the description leaves important call details unresolved, such as feedpath formatting and siteUrl representation. The minimum viable context for correct invocation is not fully met.

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%, so the description must compensate, but it does not explain what siteUrl or feedpath mean or their expected formats. The wording 'property' and 'sitemap' loosely maps to the two parameters, but an agent cannot determine precise values from the text.

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') and resource ('a submitted sitemap from a Search Console property'), making the tool's purpose clear. It does not explicitly differentiate from sibling gsc_batch_delete_sitemaps, but the singular wording and title distinguish it enough for basic selection.

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?

No guidance is provided about when to use this single-delete tool versus its sibling gsc_batch_delete_sitemaps, or when deletion is appropriate. The only usage hint is the OAuth scope prerequisite, which is a permission constraint, not an alternative-selection rule.

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