publish_post

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

With no annotations, the description partially discloses behavior by noting it 'skips the schedule queue.' However, it does not mention whether the operation is reversible, what happens if the post is already published, or any side effects like notifications.

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 sentences, no unnecessary words. Could be slightly improved by separating the purpose and behavioral note, but overall efficient.

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 the low complexity (1 param, no nested objects or output schema), the description covers the core action and a key behavior. However, it lacks context on error conditions, prerequisites, or return value, making it adequate but not thorough.

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?

With schema description coverage at 0%, the description does not clarify the 'postId' parameter beyond the schema's property name. It could have specified what kind of ID (e.g., from create_post) or any constraints. This is a missed opportunity.

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 the action ('Publish') and resource ('draft post'), and distinguishes itself from sibling tools like create_post and update_post by specifying the behavior ('Immediately. Skips the schedule queue.').

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 implies usage for publishing draft posts that are ready, but lacks explicit guidance on when not to use it (e.g., for scheduled publishing or if the post is already published). No prerequisites or alternatives are mentioned.

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