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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds genuinely new context — the side effect of re-publishing the blog so the page disappears, and the recoverability path via the site's version history in the dashboard. It stops short of stating auth/permission requirements or whether the call is immediate and permanent outside that recovery window.

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?

Three short sentences, front-loaded with the action, each carrying distinct information (what it does, the visibility side effect, the recovery route). No waste.

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 2-parameter destructive tool with no output schema, the definition covers the essential behavioral facts: the side effect and the undo path. Only minor gaps remain (whether anything is returned, whether the caller must be the owner).

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% — both `site` and `slug` are documented with an example in the schema — so the description adds no parameter meaning and the baseline of 3 applies.

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 a specific verb and resource ("Deletes a post from a Pagehaus site's blog") that clearly distinguishes it from siblings like delete_file, list_posts, and write_post. It doesn't explicitly name the near-alternatives, but the scope is unambiguous.

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?

Usage is implied by the verb and resource rather than stated: nothing says when to delete vs. unpublish via write_post, or that this is irreversible at the tool level. The conditional about public posts hints at behavior but is not framed as guidance for choosing the tool.

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