delete_sitemap

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive operation. The description adds that it returns a success message or error details, but does not disclose irreversibility, side effects, or idempotency nuances beyond the annotations.

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 extremely concise and well-structured: a clear one-line purpose, an Args section explaining the parameter, and a Returns section. Every sentence earns its place with no redundancy.

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 single-parameter tool with destructive annotations and no output schema, the description covers the action, argument, and return format. It does not mention prerequisites (e.g., GSC access setup) or side effects, but the annotations and sibling tools provide enough context for this low-complexity tool.

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?

The schema only specifies sitemap_url as a required string with 0% description coverage. The description compensates by explaining it as 'Full URL of the sitemap to delete', which adds meaningful semantics the schema lacks.

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 'Delete a sitemap from Google Search Console' with a specific verb and resource, clearly distinguishing it from sibling tools like get_sitemaps and submit_sitemap. The action is unambiguous and directly reflects the tool name.

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 explicit guidance is provided about when to use this tool versus alternatives. The sibling list (e.g., get_sitemaps, submit_sitemap) implies its role in the sitemap lifecycle, but the description does not name when to prefer this tool or exclude other tools.

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