wordpress_publish_post

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

No annotations are provided, so the description carries full burden. It states the action ('Publish') which implies a mutation, but doesn't disclose behavioral traits like required permissions, whether it's reversible (e.g., can unpublish), side effects (e.g., triggers notifications), or error conditions (e.g., invalid postId). The description is minimal and lacks context beyond the basic action.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to scan. Every word ('draft or pending', 'immediately') adds value without redundancy.

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 tool's complexity (a mutation with no annotations, 1 parameter at 0% schema coverage, no output schema), the description is incomplete. It lacks parameter details, behavioral context (e.g., permissions, side effects), and output information. For a publish operation, more guidance is needed to ensure correct usage.

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%, so the description must compensate. It doesn't mention the 'postId' parameter at all, leaving it undocumented. The description adds no meaning beyond what's inferred from the tool name (e.g., that a post is involved), failing to explain what postId represents or where to get it.

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 the resource ('a draft or pending post'), with the qualifier 'immediately' adding specificity. It distinguishes from siblings like 'wordpress_create_post' (creation) and 'wordpress_update_post' (general update), but doesn't explicitly contrast with 'wordpress_schedule_post' (delayed publishing).

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 draft/pending posts but doesn't provide explicit guidance on when to use this versus alternatives like 'wordpress_update_post' (which might handle status changes) or 'wordpress_schedule_post'. No prerequisites (e.g., post must exist, user must have publish permissions) or exclusions are mentioned.

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