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

The description does not disclose behavioral context beyond the annotations. The destructiveHint annotation already signals mutation/deletion risk, and the description merely repeats 'Unpublish post' without explaining side effects, reversibility, permission needs, or impact on the post.

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 very short, but this reads as under-specification rather than effective conciseness. A useful description would briefly explain the unpublish action and its scope while remaining succinct.

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?

Given this is a destructive, platform-scoped tool with meaningful sibling tools, the description is not complete enough. It does not clarify what 'unpublish' does, contrast with related posts tools, or explain what happens to the post.

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 has 100% description coverage, so the schema carries most of the parameter meaning. However, post_id is only described as '(required)', and the tool description adds no further semantic value to either parameter.

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?

Tautological: description restates name/title.

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 is given about when to use this tool versus siblings like posts_delete, posts_publish_now, or posts_retry. The agent is left to infer use cases and exclusions entirely from the tool name and parameter hints.

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