ghost_delete_page

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does state that deletion is 'permanent', which is a critical irreversible effect. However, it does not mention potential side effects (e.g., removal of related content, permissions needed, or whether the action can be undone). This is partially covered 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 a single, focused sentence with no wasted words. The core action and key qualifier ('permanently') are front-loaded, 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 delete-by-ID operation with one parameter and no output schema, the description is adequately complete. It covers what is deleted, how (by ID), and the permanence. Minor gaps like response format or error handling are acceptable given the simplicity and lack of complex dependencies.

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 already fully documents the single parameter 'id' with a clear description. The tool description adds no additional meaning beyond the schema, meeting the baseline for 100% schema coverage.

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), the resource (static page), and the scope (permanently by ID). It is unambiguous and distinguishes from siblings like ghost_delete_post or ghost_delete_tag by explicitly naming 'static page'.

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 on when to use this tool versus alternatives, prerequisites, or confirmations. While the action is obvious, the description does not mention that deletion is irreversible beyond the word 'permanently' or suggest when one would choose to delete a page vs. a post.

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