Searchconsole.Sitemaps.Delete

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

No annotations are provided, so the description carries the full burden for a destructive mutation. The word '(guarded)' hints at a confirmation gate but never explains that a confirm parameter exists, what value satisfies it, what failure looks like, or whether deletion is reversible. That is a significant gap for a delete 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?

A single short, front-loaded sentence with no waste, but the terseness comes at the cost of under-specification rather than efficiency; the parenthetical '(guarded)' is compressed to the point of ambiguity.

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?

An output schema exists, so return values need not be explained. But for a destructive, annotation-free tool with zero schema documentation, the description omits confirmation mechanics, permission requirements, and irreversibility — the essentials an agent needs to invoke it safely.

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% across 3 parameters. The description implies feedpath and site_url by their plain-language equivalents, but says nothing about the odd third parameter 'confirm' (nullable string, default null) — '(guarded)' only gestures at it without defining its accepted values or semantics.

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?

States a specific verb and resource: 'Delete a sitemap feed path for a property.' An agent can distinguish it from siblings like searchconsole.sitemaps.list and searchconsole.sitemaps.submit. It stops short of 5 because 'feed path' and 'property' mapping to feedpath/site_url is left implicit.

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 statement of when to use this versus sitemaps.submit or sitemaps.list, and no prerequisites (e.g., sitemap must exist, ownership verification). The agent gets no routing guidance beyond the verb.

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