pressable_delete_site

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

The description is nearly a tautology of the tool name and provides no additional behavioral context. For a destructive action, it should reveal that deletion is irreversible, what cascading effects occur (e.g., related domains, backups), or any prerequisites. No annotations are provided to compensate.

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 short sentence with no fluff. It is front-loaded and easy to parse, though the phrase 'specific' is slightly redundant. It earns brevity points but suffers from under-specification.

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 operation with no annotations and no output schema, the description is severely incomplete. It lacks any mention of irreversibility, side effects, prerequisites, or expected results. Given the large sibling set, more context is essential to avoid accidental misuse.

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 already documents the single required parameter 'id' with a clear description ('The site ID or name to delete'). The tool description adds nothing new, but with 100% coverage, the schema carries the meaning, warranting the baseline score of 3.

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 (delete) and the resource (site), and 'specific' indicates it targets one site. It distinguishes from other site-related actions like list, create, or update, though it doesn't explicitly note that deletion is permanent.

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 given on when to use this tool versus alternatives. For instance, there's no mention that disable_site might be a non-destructive alternative for temporarily taking a site offline. The description simply states the action without any usage context.

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