Delete Search Console property

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description aligns with 'Remove'. It adds context that the property must be 'existing' and scoped to the user's account. The parameter description further warns that an incorrect format returns a permission error even for an owner, which is extra behavioral nuance 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 a single, front-loaded sentence with no filler. It conveys the action and object immediately without wasting tokens.

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 destructive operation with one well-documented parameter, annotations conveying destructive behavior, and an output schema present, the description is sufficient. It does not need to explain return values or side effects beyond what annotations and the schema already cover.

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 single parameter site_url has 100% schema description coverage, including exact format, examples, and a warning about wrong formats. The tool-level description adds no parameter information, but the schema fully compensates, so the baseline of 3 applies.

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 verb ('Remove') and a clear resource ('existing website property from your Google Search Console account'). This distinguishes it from sibling tools like sitemaps.delete (which targets sitemaps) and sites.add (which adds a property).

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 makes the intended use clear: deleting a Search Console property. It does not explicitly name alternatives or exclusions, but the resource distinction is obvious from the title and sibling list. The schema's note to 'call sites.list first if unsure' is parameter guidance rather than tool-selection guidance.

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