create_bulk_job

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose potentially destructive actions ('destroy_all', 'restore_all') and overwrite behavior ('cmf_overwrite_mode (skip/overwrite)'), which adds useful transparency. However, it does not explain whether the job runs asynchronously, what side effects occur on invocation, or any permission requirements beyond a hint in the schema ('rerun_auto_tag super-admin only'). The description is informative but not fully transparent about the execution model and downstream effects.

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 well-structured as a bulleted list of operation types, front-loading the core purpose and then organizing parameters into logical groups. Every sentence adds useful information without redundancy. It is appropriately sized for the tool's complexity—comprehensive yet scannable.

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 tool's high complexity (26 parameters, rich schema, no output schema), the description is relatively complete: it covers the major operation types and parameter combinations. However, it misses the rename-preset and remove-from-group parameter groups, and it does not mention what the job returns (e.g., a bulk job ID for tracking via get_bulk_job). These gaps are notable but not severe, so the description is close to complete for a tool of this scope.

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?

Although schema description coverage is 100%, the description adds significant value by grouping parameters into high-level operation categories (e.g., 'Metadata updates: use description + description_mode, rating, rights_package_id') and explaining which parameters work together. This goes beyond the schema's individual field descriptions. However, it omits some parameter clusters such as rename operations (rename_preset_id, rename_custom_text) and remove-from-group operations (remove_asset_group_id, remove_asset_group_type), leaving some combinations undocumented.

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 clearly states 'Create a bulk job for batch operations on assets' and then enumerates specific operation types (tags, metadata, organization, AI, bulk actions), which distinguishes it from more specialized sibling tools like bulk_edit_assets or bulk_add_tags_to_assets. The verb 'create' plus the resource 'bulk job' and the detailed scope make the purpose unmistakable.

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 by listing what each operation type entails (e.g., 'Tag management: use tag_names + tag_mode') and how to combine parameters. However, it does not explicitly state when to prefer this tool over alternatives like bulk_add_tags_to_assets or bulk_set_asset_rights_package, nor does it mention when not to use it. This is close to a 4 but lacks explicit exclusions.

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