wordpress_delete_page

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

No annotations provided, so description carries full burden. It discloses the critical behavioral distinction between soft delete (trash) and hard delete (permanent), but omits reversibility details, side effects (e.g., child page handling), and return value structure.

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?

Two short sentences with minimal redundancy. The '[UNIFIED]' tag at the start appears to be implementation metadata leakage rather than helpful context, slightly degrading the signal-to-noise ratio.

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?

With zero schema descriptions, no annotations, and no output schema, a deletion tool requires richer parameter documentation and behavioral context. The description covers basic operation modes but fails to document the site identifier format or specific consequences of the operation.

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 0%, requiring heavy description compensation. While 'permanently delete or move to trash' conceptually maps to the force parameter's behavior, the description doesn't explicitly link these concepts to parameter names, leaving site and page_id completely undocumented.

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?

States specific verbs (delete/trash) and resource (WordPress page). The '[UNIFIED]' prefix is noise metadata, and while it implies the target resource type (distinguishing from siblings like wordpress_delete_post), it doesn't explicitly clarify when to choose this over similar tools.

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?

Implies usage distinction through 'permanently delete or move to trash,' indicating two modes of operation, but lacks explicit guidance on when to use this tool versus wordpress_delete_post or wordpress_delete_media, and doesn't state prerequisites like site authentication.

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