delete_site

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

With no annotations provided, the description must disclose behavioral consequences. It states the action ('Remove') but does not mention irreversibility, required permissions, or effects on associated data, which is a significant gap for a destructive operation.

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 consists of a single, clear sentence followed by a focused argument explanation. It is front-loaded, concise, and every part serves a purpose without wasting words.

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 delete tool, the description covers the core behavior and parameter format effectively. The presence of an output schema reduces the need to explain return values, but the lack of side-effect information (e.g., irreversibility) is a minor gap, keeping it from a perfect score.

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 input schema only defines site_url with no description, so schema coverage is 0%. The description compensates fully by providing exact match requirements, concrete examples (https://example.com, sc-domain:example.com), and clarifying the format for domain properties, adding essential meaning beyond the bare 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?

The description clearly uses a specific verb ('Remove') and resource ('a site from your Search Console properties'), making the tool's purpose immediate and unambiguous. It distinguishes itself from sibling tools like add_site (adding) and list_properties (listing).

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 provides clear context that this tool is for removing a site, giving no exclusions. It does not explicitly mention alternatives, but the verb 'remove' and the URL format guidance make its usage context clear, which earns a 4 rather than a 5.

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