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

Annotations confirm destructiveHint=true, and the description goes well beyond them: posts are renumbered down, listing cards move, a surplus article page is deleted with the post unless keepPages says otherwise, and a numbering hole leaves an empty card. This covers exactly the side effects an agent must anticipate before a destructive call.

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 action is front-loaded and every sentence carries rationale, but the historical aside ('Before this the only way... three deletions cost two extra pages') is longer than strictly needed to guide invocation.

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 output schema and three simple params, the description supplies ample behavioral context for a destructive operation. It omits return confirmation and any permission requirements, but nothing else needed to call it correctly is missing.

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 67%; postNumber's 1-based convention is documented in the schema, and the description adds the behavioral meaning of keepPages ('The surplus article page goes with the post, unless keepPages says otherwise'). projectId remains undocumented in both places, a minor gap.

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?

Opens with a specific verb+resource: 'Delete one blog post.' It immediately distinguishes itself from siblings like uichemy_remove_page by naming the exact entity and the numbering mechanism involved.

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?

It explains why this tool exists versus the prior approach ('the only way to remove a post was to overwrite the whole list positionally'), giving clear context for when to reach for it. It does not, however, name a sibling alternative or state preconditions explicitly.

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