wordpress_create_post

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

No annotations provided, so description carries full burden. Fails to disclose: default status behavior (draft), return value format (post ID? full object?), authentication requirements, error handling (duplicate slug behavior), or side effects. Only mentions feature support without behavioral context.

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. However, the '[UNIFIED]' prefix appears to be metadata leakage rather than helpful context for tool selection. Otherwise efficient structure with purpose first, features second.

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?

With 9 parameters, 0% schema coverage, no annotations, and no output schema, this mutation tool requires substantial descriptive support. Missing: return value documentation, parameter format specifications for complex fields (categories/tags as comma-separated strings?), and safety/disclosure text for a write operation.

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 has 0% description coverage for 9 parameters. Description mentions 4 parameters (slug, categories, tags, featured_media) but provides no semantic detail on expected formats (e.g., are categories comma-separated names, IDs, or slugs? Is featured_media an ID or URL?). Leaves 5 parameters (site, title, content, status, excerpt) completely undocumented.

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?

States 'Create a new WordPress post' with specific verb and resource. Lists supported features (slug, categories, tags, featured image). However, lacks differentiation from siblings like wordpress_create_page or wordpress_create_custom_post, which is critical given the sibling list contains both standard and custom post creation 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?

Provides no guidance on when to use this versus wordpress_create_page or wordpress_create_custom_post. No mention of prerequisites (e.g., authentication, site connection) or when NOT to use (e.g., for bulk operations where wordpress_advanced_bulk_update_posts might be better).

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