wordpress_create_page

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

With no annotations provided, the description must fully disclose behavioral traits, but it does not. It fails to mention permissions, whether the page is published as draft, what happens with hierarchy, or the return value. The phrase 'hierarchy support' is an unsubstantiated claim since the schema only accepts 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 with no redundant content. The phrase 'with hierarchy support' is vague and arguably wastes words, but overall the structure is appropriately concise.

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 simple two-parameter creation tool, the description is still incomplete. It lacks parameter semantics, behavioral details, expected output, and an explanation of 'hierarchy support.' The absence of annotations and output schema heightens the need for a more comprehensive description.

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%, so the description should compensate by explaining parameters, but it does not. The field names 'title' and 'content' are self-explanatory, yet the description adds no extra meaning and 'hierarchy support' does not map to any schema property, potentially misleading the agent.

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 a new WordPress page') and the resource, distinguishing it from post creation and page updates/deletions. However, 'with hierarchy support' is vague and does not clarify how hierarchy is implemented, slightly muddying the purpose.

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 intended use is implied by the tool name and description (creating pages), but there is no explicit guidance on when to use this tool versus alternatives like wordpress_create_post or wordpress_update_page. No 'when' or 'when not' conditions are provided.

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