Bulk Assign Categories/Tags to Posts from CSV

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

The description discloses key behavioral traits beyond annotations: it replaces existing terms, auto-creates missing tags, defaults to dry_run=true, and requires specific CSV columns. This aligns with destructiveHint=true and readOnlyHint=false, adding valuable specifics without contradiction.

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?

Two short paragraphs with front-loaded purpose and safety warnings. Every sentence adds value: purpose, required columns, dry-run default, replacement behavior, and merge guidance. No redundancy.

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 the tool's purpose, input format, safety defaults, and merge strategy, which is sufficient for a moderately complex CSV-based bulk operation. It does not describe error handling, but the stop_on_error parameter implies this and no output schema exists to explain returns.

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 description adds semantics for term_names (replace vs merge) and dry_run default, which the schema does not fully explain. Schema covers csv_path, response_format, and auto_create_missing, but stop_on_error is not clarified. This partially compensates for the 60% schema description coverage.

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 'Assign categories or tags to many posts using term NAMES (not IDs)', which is a specific verb + resource + method. It clearly differentiates this bulk taxonomy tool from sibling tools like wp_bulk_update_posts or singular create/update category/tag tools.

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 states the tool is for bulk assignment from a CSV and explicitly warns that it REPLACES existing terms, advising to include existing terms if merging is desired. This provides clear usage context, though it does not name specific alternative tools for exclusion.

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