wordpress_create_taxonomy_term

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

With no annotations, the description must disclose behavior. It mentions support for parent terms in hierarchical taxonomies, which adds transparency. However, it does not mention any side effects, error states (e.g., duplicate term), or required permissions for creation. The description is adequate but not comprehensive.

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 very short—one sentence plus a brief note. It front-loads the core action and differentiator. However, for a tool with 5 parameters, more detail would be beneficial without being verbose.

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 5 parameters, no output schema, and no annotations, the description is insufficient. It covers the basic purpose but lacks details on required parameters, return values, and error conditions. An agent would need additional information to use it 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%, so the description should explain parameters. It only mentions parent support, leaving name, site, taxonomy, and description unexplained. The parameters' meanings and required nature are not clarified, providing little 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 it creates a new term in a taxonomy, with specific support for hierarchical taxonomies. The phrase 'Works with any registered taxonomy' differentiates it from sibling tools like wordpress_create_category or wordpress_create_tag, which are limited to specific taxonomies.

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 description implies usage for any taxonomy but does not explicitly state when to use this tool versus create_category or create_tag. No guidance on when not to use it or prerequisites like authentication or existing taxonomy are provided.

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