wp_create_post

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

With no annotations, the description must disclose side effects itself. It clearly says posts are created and that dry-run previews avoid writing. However, it does not explain default status behavior, whether the post is immediately published, or what permissions or side effects are involved.

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 two short sentences with the core action front-loaded. Every word earns its place, and there is no redundant framing or filler.

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?

For a 12-parameter mutation tool with no output schema, no annotations, and low schema coverage, this description is far too minimal. An agent could infer the basic creation intent but lacks enough context about required inputs, status handling, and how dry-run output differs from real creation.

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 only 8%, so the description should compensate for the 12 undocumented parameters, but it does not. 'Supports dry-run previews' only restates the dry_run parameter's existing schema description; title, status, categories, tags, author, and other fields are left entirely to inference.

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 states a specific verb and resource: 'Create a WordPress post.' This is unambiguous against siblings like wp_create_page and wp_update_post, and the noun 'post' clearly differentiates it from page/category/tag 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?

No guidance is given on when to use this tool instead of alternatives. Sibling names imply a choice between post/page/category creation and update/delete flows, but the description does not help an agent decide.

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