Delete Staging Site

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

No annotations are provided, so the description carries full burden but fails to disclose behavioral traits. It doesn't indicate whether deletion is permanent or reversible, what permissions are required, if it affects associated resources (e.g., pages, sections), or any rate limits. This is inadequate for a destructive operation with zero annotation coverage.

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 appropriately sized and front-loaded, though its brevity contributes to gaps in other dimensions like purpose clarity and behavioral transparency.

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 destructive tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as the irreversible nature of deletion, error handling, or what happens to dependent resources (e.g., pages, sections). Given the complexity and sibling tools like revert_staging_site, more guidance is needed.

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 100%, so the schema already documents all three parameters (contentSiteId, reason, stagingSiteId) with basic descriptions. The description adds no meaning beyond this, such as explaining parameter relationships (e.g., stagingSiteId must belong to contentSiteId) or format details, but the baseline is 3 when schema coverage is high.

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 'Delete a staging site' is a tautology that restates the tool name and title without adding specificity. It doesn't clarify what resource is being deleted (e.g., a temporary development environment) or distinguish it from sibling tools like delete_content_site or delete_staging_site_page, which target different resources.

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. It doesn't mention prerequisites (e.g., needing a staging site to exist), exclusions (e.g., not for published sites), or relationships with sibling tools like revert_staging_site or publish_staging_site, which might be relevant alternatives.

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