delete_sitemap

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

With no annotations, the description must disclose side effects and safety traits. It only labels the operation as 'Delete (unsubmit)' without detailing permanence, required permissions, or post-deletion effects. The domain property note is more about parameter usage than behavioral 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-sentence purpose followed by a clean Args list. Every sentence adds value, and the structure is front-loaded with the core action.

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 delete operation, the description covers the required inputs and their semantics. The existing output schema handles return values, so no additional return info is needed. It lacks explicit prerequisites like property ownership, but the site_url reference to list_properties indirectly covers that.

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 provides no descriptions for the two parameters, so the description's Args section is essential. It explains the site_url format with examples and the domain property nuance, and defines sitemap_url clearly. This fully compensates for the empty schema.

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 clearly states the tool's action: 'Delete (unsubmit) a sitemap from Google Search Console.' This specifies a verb and resource, distinguishing it from sibling tools 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?

The description implies usage by naming the action ('Delete'), but it does not explicitly state when to use this tool versus alternatives such as submit_sitemap or manage_sitemaps. The domain property note provides context for site_url selection but not tool selection.

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