wordpress_create_post

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

No annotations are provided, so the description carries the full burden. It only lists supported features but does not disclose important behavioral traits such as required permissions, error handling, side effects (e.g., whether duplicate titles are allowed), or the nature of the response.

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 concise sentence that front-loads the core purpose. The '[UNIFIED]' prefix is somewhat unclear but does not harm clarity. It could be slightly expanded without losing conciseness.

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 9 parameters (3 required), no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, or the format of parameters like tags (e.g., comma-separated string). An agent would lack critical information to use this tool 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 description adds meaning to four parameters (slug, categories, tags, featured_media) by stating they are supported. However, it omits description of the five other parameters (site, title, content, status, excerpt) including the three required ones. Schema coverage is 0%, so the description partially compensates but is incomplete.

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 'Create a new WordPress post' which is a specific verb+resource. It mentions supported features (custom slug, categories, tags, featured image) which helps distinguish from wordpress_create_page. However, it does not differentiate from wordpress_create_custom_post, a sibling that creates custom post types.

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 provided on when to use this tool versus alternatives like wordpress_create_page or wordpress_create_custom_post. There is no mention of prerequisites, context, or when-not-to-use.

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