wordpress_create_category

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

No annotations are provided, so the description carries full burden. It mentions 'hierarchical support', hinting at parent-child relationships, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, error handling, or what happens on duplicate names. For a mutation tool with zero annotation coverage, this is insufficient.

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, efficient sentence with zero waste. It's front-loaded with the core action and includes a useful detail ('hierarchical support'). Every word earns its place, making it highly concise and well-structured.

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 a mutation tool with no annotations, 0% schema coverage, no output schema, and 1 parameter, the description is incomplete. It lacks details on behavior, parameters, return values, and usage context. While concise, it doesn't provide enough information for safe and effective tool invocation in a complex WordPress environment.

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%, with 1 parameter ('name') undocumented in the schema. The description adds no parameter details beyond implying a category name is needed. It doesn't explain format, constraints, or optional fields like parent ID for hierarchy. Baseline is 3 due to low coverage, but the description fails to compensate adequately.

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 category') and resource ('category'), specifying it supports hierarchy. It distinguishes from siblings like 'wordpress_create_term' (general) or 'wordpress_create_tag' (non-hierarchical), but doesn't explicitly contrast them. The purpose is specific and actionable.

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 like 'wordpress_create_term' or 'wordpress_update_category'. The description implies creation of a category, but lacks context on prerequisites, permissions, or typical use cases. It's a basic statement without operational context.

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