wp_posts_publish

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

With no annotations, the description carries the full burden. It states the core behavior (sets status to 'publish'), clarifies it operates on an existing post (not creating), and discloses the 'publish tier' permission requirement. It does not mention return values or idempotency, but for a simple mutation this is acceptable.

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 concise sentences that front-load the core action and effect, then add the shortcut relationship and the tier requirement. No wasted words.

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 simple one-parameter tool with no output schema, the description covers the action, the resulting state, the prerequisite permission, and how it relates to an alternative tool. It is fully complete for an AI agent to select and invoke correctly.

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 only 'id' with no description coverage. The description compensates by explaining that the id refers to an existing post, providing essential semantic meaning. It doesn't go into further detail, but for a single parameter this is sufficient.

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 description clearly states a specific verb ('Publish') and resource ('an existing post by id'), and explicitly defines the effect as setting status to 'publish'. It also differentiates itself from wp_posts_update by being a shortcut, making its purpose unambiguous relative to sibling 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?

The description provides clear context: use this to publish an existing post by id, and it's a shortcut for wp_posts_update with status='publish'. It also mentions the 'publish tier' requirement. However, it does not explicitly state when NOT to use it (e.g., for scheduling, use wp_posts_schedule), leaving some implicit inference.

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