pob_set_config

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to explain what is destroyed or replaced — it says nothing about whether existing config entries are overwritten, whether the call is all-or-nothing, or what validation errors look like. The only extra sentence, "Выполняет ConfigTab:BuildModList", is an internal implementation detail that conveys no agent-facing behavior.

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 definition is short and front-loads the intent, which is good, but the second sentence about ConfigTab:BuildModList does not earn its place for an agent caller, and the remaining text is too compressed to be actionable.

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?

This is a destructive, closed-world mutation taking an untyped free-form object with no output schema and no annotations beyond hint flags, so the description should explain the accepted structure, the catalog dependency, and overwrite semantics. It omits all three, leaving an agent unable to call it safely.

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 coverage is 0% and the sole parameter is a free-form nested object with additionalProperties=false, so the description carries the full burden. Saying values must use "exact names, types and values of the config catalog" gives a hint about valid keys and typing, but no shape, key names, or example of the object is provided, leaving the agent unable to construct a valid payload.

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 names a specific verb ("Установить", set) and resource (config calculation conditions), but the qualifier "по точным именам, типам и значениям каталога config" is opaque without knowing what the config catalog is, and the reference to an internal method ("ConfigTab:BuildModList") adds no distinguishing information. It does not clearly separate this tool from the sibling pob_set_custom_mods, which also mutates build configuration.

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 when-to-use or when-not-to-use guidance and no mention of the natural prerequisite of calling pob_catalog first to obtain valid names/types. The agent must infer that this tool applies configuration discovered elsewhere and must choose it over pob_set_custom_mods without any stated rule.

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