wordpress_create_category

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

No annotations provided, so description carries full burden. It adds valuable behavioral context by disclosing hierarchical support/parent relationships, which affects how the tool behaves compared to tag creation. However, missing: auth requirements, idempotency guarantees, error handling (what happens if parent category doesn't exist?), rate limits, or side effects.

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?

Appropriately concise at two sentences. The '[UNIFIED]' prefix appears to be metadata tagging but doesn't obstruct clarity. Front-loads the primary action in the first sentence, with implementation detail (hierarchical) in the second. No redundant or wasted text.

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?

Severely constrained by zero schema descriptions, no annotations, and no output schema. For a 4-parameter creation tool, the description should compensate more aggressively for the missing structured metadata. Lacks: return value explanation (created category ID? full object?), error conditions, or prerequisite validation rules. Incomplete given the richness gap in structured fields.

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 has 0% description coverage. Description mentions 'parent relationships' which implicitly documents the 'parent' parameter accepting null or a parent ID. However, fails to explain critical parameters: 'site' (is this a URL, ID, or slug?), 'name' (format constraints?), and 'description' (optional nature). With zero schema coverage, the description inadequately compensates for undocumented parameters.

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?

States specific verb (Create) + resource (WordPress category) clearly. The mention of 'hierarchical categories with parent relationships' adds scope specificity and implicitly distinguishes from flat taxonomies like tags (sibling wordpress_create_tag). However, it does not explicitly differentiate from wordpress_create_taxonomy_term or clarify when to prefer this over the generic taxonomy term creator.

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?

Provides no guidance on when to use this tool versus alternatives like wordpress_create_tag (for flat classification) or wordpress_create_taxonomy_term (for custom taxonomies). No prerequisites mentioned (e.g., site must exist, parent ID must be valid category). No exclusion criteria or 'when not to use' context.

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