remove_site

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

No annotations are provided, so the description carries full burden. 'Remove' implies a destructive mutation, but the description doesn't disclose whether this action is reversible, requires specific permissions, has rate limits, or what happens to associated data. It lacks behavioral context beyond the basic action.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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?

Given the tool has an output schema (which handles return values), 1 parameter, and no annotations, the description is minimally complete for a simple removal operation. However, as a destructive mutation tool with no behavioral disclosure, it should provide more context about effects and prerequisites to be fully adequate.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'a site' but doesn't clarify what 'site_url' should contain (e.g., format, domain requirements). With 1 parameter and no schema descriptions, the description adds minimal semantic value beyond implying the parameter identifies the site.

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') and the resource ('a site from Bing Webmaster Tools'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'remove_sitemap' or 'remove_site_role', which also remove resources from the same platform.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the site must exist in Bing Webmaster Tools), exclusions, or when to choose other removal tools like 'remove_sitemap' or 'remove_site_role'.

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