run_post_install_task

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

Annotations already indicate this is not read-only and not strictly destructive. The description adds that execution happens via Jenkins/Ansible and gives an example side effect (installing GPU drivers), but it does not disclose potential consequences, reversibility, or long-running behavior. No contradiction with 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?

A single front-loaded sentence states the action, source of task identifiers, and a concrete example. Every clause earns its place, and there is no redundant filler.

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?

With a fully described schema and no output schema, the description covers the primary invocation path: server ID, task from list_post_install_tasks, optional params, and the confirm gate. It could mention asynchronous behavior or return value expectations, but nothing essential to calling the tool correctly is missing.

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 100%, so parameters are fully documented by the schema. The description adds no materially new meaning beyond restating that task is an ID/name from list_post_install_tasks and that extra parameters are supported.

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 action ('Выполнить Jenkins/Ansible-задачу на сервере') and a clear resource (a task selected from list_post_install_tasks). The example of installing GPU drivers after OS reinstall makes the tool's purpose concrete and distinguishes it from the sibling listing tool.

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 directs the agent to source valid task identifiers from list_post_install_tasks and gives a realistic context ('после переустановки ОС'). It does not explicitly mention alternatives or exclusion criteria, but the intended use is clear enough for correct selection.

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