wp_create_content

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it creates content (a write/creation operation), but provides no details on permissions, side effects (e.g., immediate visibility on publish), or consequences of the action. No extra behavioral context is offered beyond the basic verb.

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 sentences with no fluff, front-loaded with the purpose. For a tool with 21 parameters, keeping the description short is appropriate since the schema handles parameter details. It is concise but could arguably add a tiny bit more context without becoming wordy.

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 complexity (21 parameters, multiple post types, WooCommerce variations), the description covers the high-level purpose and the WooCommerce special case, but omits important details like the requirement to set type='product' for WooCommerce fields, the default status (draft), and what the return value contains. The schema compensates for some gaps, but the description leaves room for confusion.

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 100%, so all parameters are already documented. The description highlights the WooCommerce-specific parameters (prices, SKU, stock), but these are also described in the schema with the 'WooCommerce:' prefix, so the description adds minimal new meaning. It groups them but does not clarify usage beyond what the schema provides.

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 'Create' and the resource 'new WordPress post, page, or product', which immediately distinguishes it from update, list, and delete operations. It also mentions WooCommerce product specifics (prices, SKU, stock), adding specificity without ambiguity.

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 verb 'Create' implies this tool is for new content, but the description does not explicitly reference sibling tools like wp_update_content or wp_list_content, nor does it state when to use this instead of those. Usage is implied rather than explicitly guided.

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