batch_create_catalog_overrides

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

With no annotations supplied, the description bears the full burden of disclosure, and it is a write/mutation tool that produces a new package file. It reveals one useful default (implicit scan of SIMS4_MODS_DIR when no sources are passed) but says nothing about whether an existing output package is overwritten, whether source packages are modified, or what permissions/environment are required.

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 sentences with the bulk operation front-loaded and the fallback behavior second, so it is easy to scan. The reStructuredText double-backtick markup is noise in a tool description, but the text itself is tight.

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?

A 7-parameter mutation tool with four required parameters, no annotations, no output schema, and zero schema description coverage needs far more than two sentences. Missing are the semantics of filter_query, the meaning of the boolean toggles, and the shape/behavior of the produced package.

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 0% across 7 parameters, so the description must compensate, and it only covers two areas: the resource_type values (casp/cobj/objd) and the source selection fallback via source_dir/source_packages. The required parameters filter_query, disable_random_spawn, and output_package, plus hide_items, get no explanation of expected syntax or effect.

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 gives a verb ('Bulk-patch') and a resource ('CASP/COBJ/OBJD catalog flags') plus the destination ('an override package'), which is more than a restated name. However, 'catalog flags' is specialist jargon that never connects to the concrete effects exposed in the schema (hiding items, disabling random spawn), so an agent cannot confidently predict the outcome. It also does not distinguish this from siblings such as build_package.

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?

There is no statement of when to use this tool versus alternatives like build_package or inspect_package, and no prerequisites or exclusions. The only conditional sentence ('When no sources are given, SIMS4_MODS_DIR is scanned') is a behavioral default, not selection guidance.

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