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

Annotations already declare destructiveHint=true, but the description adds the crucial nuance that only the listing is removed, not Google's index — a non-obvious behavioral boundary. It also discloses the preview/confirmation_token flow, one-time 10-minute expiry, invalidation on argument changes, token cost per call, and the data_availability vocabulary. Minor gap: it doesn't say what the success payload looks like, though no output schema exists.

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?

Front-loaded with purpose and irreversibility caveat, then confirmation flow, then result semantics. Dense but each block serves the caller; the generic data_availability enumeration and the Korean quota note are somewhat boilerplate-heavy for a delete tool but still relevant given the absent output schema.

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 destructive, no-output-schema mutation tool, the description covers scope of effect, preconditions, confirmation protocol, token lifecycle, and interpretation of result states. There is nothing material an agent would need to call it correctly that is missing.

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 coverage is 100%, so the baseline is 3; the description goes further by explaining how parameters interact — the token must accompany identical arguments, and changing any argument voids it. That cross-parameter semantics is not stated in the 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?

A specific verb+resource ('Remove a sitemap URL from the sitemap list of the linked Search Console site') with an immediate scope qualifier distinguishing it from full site removal and from deindexing. The sibling sitemap__submit and site__remove are easy to tell apart after reading the first two sentences.

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?

Explicitly states the precondition (sitemap URL must be inside the selected site) and names the reversal path ('To undo, submit the same URL again with the sitemap submission tool'), which routes the agent to the sibling. It also documents the mandatory two-step confirmation protocol with its no-token-without-user-consent rule.

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