wp_create_term

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

With no annotations, the description fully discloses behavior: dry_run defaults to true and writes nothing, false performs the create, and the result is verified by reading the term back. It also warns that prod writes require allow_prod=true and that parent is ignored for tags.

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 focused and uses backticks to highlight terms, with safety caveats placed clearly. It is slightly repetitive around dry_run and prod requirements but remains efficient.

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?

The description covers preconditions, side effects, and verification, but because there is no output schema it does not state what is returned beyond the implied reading back of the term. The missing install parameter also prevents full operational context.

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?

The prose explains taxonomy, slug, parent, dry_run, and allow_prod, but the required 'install' parameter and the 'description' parameter are not explained. Since the schema has no per-parameter descriptions, this leaves gaps for two of eight 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?

The description opens with 'Create one term' and specifies the resource as 'a category, tag, or any custom taxonomy term', making the action and target unambiguous. It also distinguishes from assignment by pointing to wp_set_post_terms.

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?

It provides practical guidance: taxonomy should come from wp_list_taxonomies, parent only applies to hierarchical taxonomies, and assignment should use wp_set_post_terms. It also explains dry_run and allow_prod flags, though it does not contrast with update/delete term tools.

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