Delete Site

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

With no annotations provided, the description carries the full burden. It discloses that the operation is 'Irreversible — use with caution', which is a key behavioral trait for a destructive action. However, it does not describe side effects (e.g., whether associated data is deleted) or any authentication/ownership requirements. The warning is helpful but not comprehensive.

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 exceptionally concise—two short sentences with zero fluff. The action and the critical warning are front-loaded. Every word earns its place, making it efficient for an agent to parse.

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 tool with one parameter, full schema coverage, and an output schema present, the description covers the essential aspects: what it does and the irreversible risk. It lacks mention of permissions or prerequisites, but given the simplicity, the description is adequate. Slightly more context about consequences would make it complete.

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%, and the single parameter site_url is described as 'Property URL to remove'. The description adds no additional meaning beyond the schema, so the baseline of 3 applies. No extra semantic context is provided.

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 states the action ('Remove a property from GSC') with a specific verb and resource. It distinguishes itself from add_site and other sibling tools implicitly, though it does not name an alternative. The irreversibility warning adds clarity about the operation's nature.

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?

No guidance is provided on when to use this tool versus alternatives, such as when a user wants to permanently remove a property. There is no mention of prerequisites, permissions, or when not to use it. The description only states the action and a caution, leaving usage context entirely to the agent.

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