pages_delete_post

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

No annotations are provided, so the description carries the burden. It does disclose the key behavioral trait that deletion is permanent, but it omits other important details such as whether confirmation is required, whether deletion cascades to associated data, or any permission requirements.

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 concise sentence with no filler. However, it is overly terse given that it omits essential parameter information, so it does not fully earn a 5.

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 no annotations, no output schema, and a minimally described confirm parameter, the description leaves significant gaps. The agent cannot fully understand the deletion workflow or the role of the confirm flag from the description alone.

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 0%, and the description does not explain either parameter. The post_id is somewhat inferable from 'post', but the critical 'confirm' boolean parameter is completely unexplained, leaving the agent without guidance on how to invoke the deletion safely.

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 tool name is pages_delete_post and the description 'Delete a post permanently' clearly specifies the verb (delete), resource (post), and scope (page post, inferable from name). It is not easily confused with sibling tools like pages_publish_post or pages_get_post.

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 when-to-use or when-not-to-use guidance is provided. The description implies the tool is for deleting a post, but it does not mention alternatives, prerequisites, or the need for confirmation.

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