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

It adds substantial behavioral context beyond the annotations: default draft status, language placement and fallback behavior on multilingual vs single-language sites, how meta and template actually affect the created page, and the Connector version requirement. The readOnlyHint=false and destructiveHint=false annotations are consistent with the described creation behavior.

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 front-loaded with purpose and then organized by use case, with no obvious filler. It is somewhat lengthy, but the detail is largely warranted by the number of non-obvious parameters and the advanced WordPress scenarios covered.

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 output schema exists, so return values need not be explained, and the annotations cover the basic safety profile. The description covers the hardest operational details for multilingual and page-builder workflows, but it omits important context like how to select the target site via site_url and what status values beyond the default draft are allowed.

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?

With 14 parameters and 0% schema description coverage, the description carries the burden and does explain the most complex ones: language, template, meta, and copy_meta_from. However, many basic parameters such as site_url, status, type, slug, content, excerpt, categories, tags, and featured_media receive no explanation, leaving significant gaps.

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 first sentence states a specific verb and resource: 'Create a post or page on a connected WordPress site.' It also distinguishes the default behavior ('Defaults to a draft you can review before publishing'), so an agent can tell this is the creation tool rather than an update or list tool.

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 gives clear contextual guidance for multilingual sites, page-builder templates, and meta copying, which helps choose the right parameters. It does not explicitly name when to use this versus update_post or bulk_replace, so it lacks full when-not/alternatives routing.

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