Delete sitemap

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

No annotations are present, so the description must carry full behavioral disclosure. 'Remove' implies a destructive action, but the description does not state whether the action is irreversible, whether special permissions are required, or what happens if the sitemap does not exist.

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, focused sentence with no redundant or irrelevant information. Every word contributes to the meaning.

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 delete operation with two well-specified parameters, the description covers the core action. However, with no annotations, it could benefit from noting permanence or side effects, though it remains minimally viable.

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%, with both siteUrl and feedpath clearly documented. The description adds no additional meaning beyond the schema, providing no further guidance on syntax or format.

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 action ('Remove') on a specific resource ('sitemap') within a clear context ('Google Search Console for a property'). It clearly distinguishes from sibling tools like submit_sitemap and list_sitemaps by focusing on deletion.

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 clearly implies usage when a sitemap needs to be removed from a property. It provides clear context but does not explicitly state alternatives or when not to use it, nor mention prerequisites like the sitemap having been previously submitted.

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