wordpress_create_category

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

Description claims hierarchical support but the input schema only has a required 'name' parameter with no parent field, which may confuse the agent. No disclosure of permissions, idempotency, or return values. Annotations absent so burden is on description.

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?

Single sentence is concise but lacks necessary detail; it is front-loaded with purpose but omits critical info. Appropriate length for a simple tool but insufficiently informative.

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 low complexity but many siblings, the description should differentiate from create_tag/create_term and explain taxonomy context. It does not, leaving the agent without enough information to choose correctly.

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 does not explain the sole parameter 'name' (e.g., whether it's a slug or display name). Adds no semantic value beyond the schema.

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?

Description clearly states the tool creates a category and adds 'with hierarchical support', which distinguishes it from sibling tools like create_tag or create_term. The verb 'Create' and resource 'category' are specific.

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 on when to use this tool versus alternatives such as wordpress_create_tag (tags) or wordpress_create_term (other taxonomies). No prerequisites or common scenarios mentioned.

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