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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that hiding persists ~6 months, snippets stay wiped until re-index, prefix scope can hide a whole folder or site, requests take up to a day and are not guaranteed, and crawling is not stopped. It also flags confirmation behavior and the 'reaches other people' warning, which are critical for a mutating call.

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-loads the core action and packs dense, high-value information into a compact paragraph. It is slightly run-on and dense, but virtually every sentence carries non-redundant operational detail.

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 mutating tool with no output schema, it covers everything an agent needs: permissions, confirmation flow, timing/uncertainty, scope semantics, and the permanent-removal alternative. Nothing essential 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, but the description adds real meaning: it explains that 'clear_snippet' wipes the description, that scope 'prefix' targets all URLs under a prefix (potentially an entire folder or site), and it names the property requirements. This exceeds what the enum/labels alone convey.

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: 'Temporarily remove a URL or prefix from Google results, or clear its snippet.' This clearly distinguishes the two operating modes and separates temporary removal from permanent removal. It does not explicitly name a sibling tool, but the resource is unique among its siblings.

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?

Provides clear when-to-use context (temporary removal lasting ~6 months, or clearing a snippet) and a strong when-not signal: 'For a permanent removal the page needs a 404 or 410, a password or noindex.' It also names the required permission level (Owner or Full user), giving the agent prerequisites.

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