wordpress_create_page

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

Annotations are absent, so the description must disclose behavioral traits. It mentions 'hierarchy support' but does not explain what that entails (e.g., a 'parent' parameter is missing from the schema). It also does not state whether the operation is safe, destructive, or requires authentication.

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 extremely concise (8 words), which is good, but it omits necessary details. It front-loads the main action, yet fails to provide a structured explanation of behavior or parameters, making it insufficiently informative despite its brevity.

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 simplicity (2 params, no output schema, no annotations), the description is too sparse. It lacks information about return values, error conditions, hierarchy implementation, or any side effects. A more complete description would cover these aspects.

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 0% schema description coverage, the description is expected to explain the parameters. It only references 'hierarchy support' but says nothing about 'title' or 'content' – their format, constraints, or role in page creation. The schema provides no descriptions, so the agent gains no semantic help.

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 action ('Create') and the resource ('WordPress page'), and adds 'with hierarchy support' to hint at parent-child page relationships. It implicitly distinguishes from 'create_post' for posts, but does not explicitly differentiate from other creation tools like 'create_category' or 'create_comment'.

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 provided on when to use this tool versus alternatives like 'wordpress_create_post' or 'wordpress_bulk_create_posts'. The description does not specify prerequisites, context, or exclusions.

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