wordpress_create_taxonomy_term

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully notes hierarchical support and parent-term relationships, but omits critical mutation details such as idempotency, duplicate handling, required write permissions, or return value structure.

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?

Three sentences efficiently structured with the core action stated first. The '[UNIFIED]' tag is unnecessary noise, but overall minimal waste—every remaining sentence adds distinct information about scope or behavior.

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?

Adequate for basic operation selection but incomplete for a mutation tool with zero schema annotations. It covers the hierarchical complexity specific to taxonomies, yet leaves significant gaps regarding parameter documentation, error behavior, and success indicators that should be addressed given the rich schema and lack of output schema.

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% across 5 parameters. The description partially compensates by mentioning 'parent terms' (mapping to the 'parent' parameter) and referencing 'taxonomy,' but fails to document 'site' (likely a site identifier), 'name,' or 'description' parameters, nor specify expected formats (e.g., whether 'parent' expects an ID, slug, or name).

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?

Defines a clear action (create) and resource (taxonomy term) and distinguishes itself from siblings with 'Works with any registered taxonomy,' implying it is the generic option compared to specific tools like wordpress_create_category. However, the unexplained '[UNIFIED]' prefix slightly obscures clarity.

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 explicit guidance on when to select this tool over alternatives (e.g., wordpress_create_category for categories) or prerequisites like requiring a valid taxonomy slug. Only implicit context is provided via hierarchical support.

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