wordpress_create_post

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Create a new WordPress post' and does not state whether the post is created as a draft or published immediately, what permissions are required, or any side effects. The phrase 'full control over all post properties' actively misleads because the schema restricts input to title and content.

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, front-loaded sentence, but the phrase 'with full control over all post properties' is both unnecessary and inaccurate. It adds noise rather than value, so while short, it is not fully concise in the sense of every word earning its place.

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?

The tool has no output schema and no annotations, and the description does not explain return values, post status, error handling, or any other behavioral context. For a WordPress post creation tool, this is incomplete, even though the input schema itself is simple.

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%, and the description adds no meaningful parameter guidance. Worse, 'full control over all post properties' contradicts the actual schema, which only accepts title and content, making the parameter semantics actively misleading rather than helpful.

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 verb and resource ('Create a new WordPress post'), and this distinguishes it from siblings like wordpress_update_post, wordpress_publish_post, and wordpress_create_page. However, the phrase 'full control over all post properties' is misleading given the schema only exposes title and content, so the purpose is slightly overclaimed.

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 provides no guidance on when to use this tool versus alternatives such as wordpress_schedule_post, wordpress_publish_post, or wordpress_bulk_create_posts. No context is given about prerequisites, typical use cases, or exclusions.

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