wordpress_advanced_bulk_update_media

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

No annotations are provided, so the description must carry the full burden. It discloses the 100-item limit and supported fields (alt_text, title, caption, description), but omits mutation safety details, idempotency, or whether partial failures are possible.

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 core content is efficiently structured in three sentences with the action front-loaded. Minor deduction for the '[UNIFIED]' metadata tag which consumes tokens without adding semantic value for tool selection.

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 the nested object complexity and lack of output schema, the description is minimally viable. It covers the update payload content but leaves gaps regarding return value structure, error formats, and the specific input formats for required parameters.

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?

With 0% schema description coverage, the description partially compensates by listing valid field keys for the `updates` object (alt_text, title, etc.). However, it fails to explain the `site` identifier format or the expected data type/structure for `media_ids` array items.

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?

Clearly states the action (update) and resource (media items) with scope (multiple/at once). The '[UNIFIED]' prefix is noise that doesn't aid selection, but the description effectively distinguishes this from the singular `wordpress_update_media` sibling by emphasizing 'multiple'.

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?

Provides the operational constraint 'Max 100 items per request' which guides batch sizing. However, it lacks explicit guidance on when to choose this over the single-item `wordpress_update_media` or error handling behavior (e.g., partial vs atomic failures).

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