Bulk Create Posts from CSV

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

The description discloses the critical dry_run=true default and lists required/optional CSV columns, adding behavioral context beyond the annotations. It does not contradict the annotations, which already indicate a non-read-only operation.

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 concise and front-loaded with the core purpose. The first paragraph states what the tool does and the column requirements; the second gives a clear use case. No redundant or filler content.

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 essential input format and dry-run behavior, making the tool usable. However, because there is no output schema, it should clarify what the tool returns (e.g., created post IDs or a summary) and error handling, which are missing. This is a notable gap for a bulk write operation.

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 schema already provides descriptions for csv_path and response_format (50% coverage). The description echoes the CSV column information and adds the dry_run default, but it does not explain stop_on_error beyond the parameter name. It adds modest value over 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?

The description opens with 'Create many posts from a CSV,' which precisely states the action, resource, and input method. It distinguishes this bulk operation from single-post tools like wp_create_post and the use case adds further 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?

The description provides a clear use case ('import a content calendar') and notes the dry_run default, which guides safe usage. However, it does not explicitly contrast with alternatives (e.g., wp_create_post) or state exclusions, so it falls short of a 5.

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