delete_site

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

With no annotations, the description must carry the full burden of behavioral disclosure. It states the core action but does not mention that deletion is likely irreversible, what cascade effects occur (e.g., sitemaps removed), whether ownership is required, or what happens on failure. For a destructive operation, this is a significant gap.

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 two efficient sentences: the action is front-loaded, and parameter details are compactly structured with clear examples. No filler or repetition.

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 one-parameter destructive tool, the operational calling information is nearly complete, and the output schema covers return values. However, the missing behavioral context around permanence, side effects, and prerequisites means the definition is only minimally adequate rather than thorough.

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 zero description for the single parameter, but the tool description thoroughly compensates: it gives exact-match requirements, concrete URL examples, and the special sc-domain: format for domain properties. This is exactly the level of detail an agent needs.

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 uses a specific verb ('Remove') and resource ('site from your Search Console properties'), making the tool's purpose unambiguous. It clearly distinguishes itself from siblings like add_site and list_properties.

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?

When to use this tool is implied by its name and action ('remove a site'), but there is no explicit guidance on when not to use it, no mention of alternatives, and no prerequisites or conditions. The context is clear enough, but the description leaves routing entirely to inference.

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