Bulk Update Media Alt Text from CSV

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

Annotations already indicate destructive and idempotent behavior. The description adds the crucial safety detail that dry_run defaults to true, which mitigates the destructive hint. It also mentions the CSV columns, though it does not fully disclose behavior like error handling or whether existing values are overwritten. Overall, it adds meaningful context beyond annotations.

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 two sentences, front-loaded with the primary purpose, and each sentence adds value. The optional columns are listed efficiently, and the use case is a concrete example without unnecessary prose.

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?

For a bulk operation tool with four parameters, the description covers the essential invocation details: CSV path, required/optional columns, and dry-run default. It lacks explicit behavior on stop_on_error and what happens with invalid rows, but the core usage is clear. The provided use case adds context that helps the agent understand when to apply this tool.

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 50% (csv_path and response_format have descriptions). The description reinforces csv_path column requirements and highlights the dry_run default, which is not in the schema. However, stop_on_error is left undocumented in both schema and description, and the description does not fully compensate for the missing schema 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 uses a specific verb ('Backfill') and explicitly states the resource ('media items') and method ('from a CSV'). It also lists the optional fields (caption/description/title), which differentiates it from sibling tools like wp_update_media (single update) and wp_bulk_update_posts (bulk posts).

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 clear context for bulk backfilling media alt text from a CSV and even gives a concrete use case. However, it does not explicitly state when to use this tool instead of alternatives (e.g., wp_update_media for single items), so it lacks explicit exclusions or alternative comparisons.

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