wordpress_create_post

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

With no annotations, the description must disclose all behavioral traits. It only mentions the default draft status and safe review, but omits other important aspects like authentication, error handling, or side effects. This is insufficient for a create operation.

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 concise with two sentences, front-loading the action and key behavior. No unnecessary words. However, it could be slightly more structured by explicitly noting required parameters.

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 (8 parameters, 1 required), no output schema, and no annotation, the description's single behavior note is insufficient. It lacks details on mandatory fields (only title) and how to use other parameters effectively.

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 only hints at the status parameter via the default draft, leaving 7 parameters (title, content, excerpt, slug, categories, tags, featuredMedia) unexplained. This is a significant gap.

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 WordPress post', which is specific and distinct from sibling tools like 'wordpress_create_page' or 'wordpress_clone_page'. It also mentions the default draft status, adding clarity.

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 that this tool creates posts and defaults to draft for safe review, but it does not explicitly guide when to use it versus alternatives like 'wordpress_update_post' or 'wordpress_delete_post'. No exclusions or context are provided.

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